Triple
T22856887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHL Mountain Division |
E566506
|
entity |
| Predicate | teamCountRange |
P18041
|
FINISHED |
| Object | 6–8 teams |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 6–8 teams | Statement: [ECHL Mountain Division, teamCountRange, 6–8 teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCountRange Context triple: [ECHL Mountain Division, teamCountRange, 6–8 teams]
-
A.
teamCountType
Indicates how the number of teams is categorized or measured within a given context.
-
B.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
C.
numberOfTeamsVariesBetween
chosen
Indicates that the count of teams involved changes within a specified range or across different instances or conditions.
-
D.
qualifiedTeamsCount
Indicates the number of teams that have successfully met the criteria to qualify for a given stage, event, or competition.
-
E.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebd7d48819085f350f2ce4144a0 |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.