Triple
T36190945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Worth Flyers |
E1046983
|
entity |
| Predicate | seasonRecord2006–07 |
P21379
|
FINISHED |
| Object | 29–21 |
—
|
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: 29–21 | Statement: [Fort Worth Flyers, seasonRecord2006–07, 29–21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecord2006–07 Context triple: [Fort Worth Flyers, seasonRecord2006–07, 29–21]
-
A.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
B.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
-
C.
regularSeasonRecord2016
Indicates the win-loss (and possibly tie) performance of an entity during the 2016 regular season.
-
D.
regularSeasonRecord1967–68
Indicates the win-loss (and possibly tie) performance of a team during the 1967–68 regular season.
-
E.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:08 p.m.