Triple
T8505448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsa Oilers (hockey) |
E201321
|
entity |
| Predicate | foundedAsECHLFranchise |
P68324
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Tulsa Oilers (hockey), foundedAsECHLFranchise, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsECHLFranchise Context triple: [Tulsa Oilers (hockey), foundedAsECHLFranchise, 2014]
-
A.
foundedAsAHLFranchise
Indicates that an organization or team was originally established as a franchise in the American Hockey League (AHL).
-
B.
formerAHLFranchiseOf
Indicates that one entity was previously an American Hockey League (AHL) franchise of the other entity, but no longer holds that status.
-
C.
foundedAsNHLDivision
Indicates that an NHL division was originally established or created in its initial form as part of the National Hockey League.
-
D.
foundedAsIceHockeyLeagueOf
Indicates that an entity was originally established in the role or form of an ice hockey league for another entity.
-
E.
joinedECHL
chosen
Indicates that an entity became a member of or started participating in the ECHL (East Coast Hockey League).
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5d8b7208190b199c56bf366c692 |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.