Triple
T26538616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quad City Flames |
E671321
|
entity |
| Predicate | servedAsAffiliateOf |
P1721
|
FINISHED |
| Object | Calgary Flames |
—
|
NE NERFINISHED |
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: Calgary Flames | Statement: [Quad City Flames, servedAsAffiliateOf, Calgary Flames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsAffiliateOf Context triple: [Quad City Flames, servedAsAffiliateOf, Calgary Flames]
-
A.
operatedAsAffiliateFrom
Indicates that one entity functioned as an affiliate of another entity starting from a specified point in time.
-
B.
partnerAffiliation
Indicates that two entities are formally associated as partners within an organization, project, or collaborative relationship.
-
C.
hasAffiliate
chosen
Indicates that one entity is formally associated with another as an affiliate, typically through a partnership, membership, or subordinate organizational relationship.
-
D.
hasAffiliatesIn
Indicates that an entity maintains affiliated entities, branches, or partners located within a specified place or region.
-
E.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 1:40 a.m.