Triple
T38366608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billings Mustangs |
E892462
|
entity |
| Predicate | hasFormerAffiliation |
P9419
|
FINISHED |
| Object | Cincinnati Reds |
—
|
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: Cincinnati Reds | Statement: [Billings Mustangs, hasFormerAffiliation, Cincinnati Reds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerAffiliation Context triple: [Billings Mustangs, hasFormerAffiliation, Cincinnati Reds]
-
A.
hasFormerInstitution
chosen
Indicates that an entity was previously affiliated with, employed by, or enrolled in a particular institution in the past.
-
B.
hasFormerInstitutionName
Indicates that an institution was previously known by a different name.
-
C.
affiliationHistory
Indicates a historical record of an entity’s past and present organizational or group affiliations, including when and how those affiliations changed over time.
-
D.
hasFormerInstitutionType
Indicates that an entity was previously associated with or classified under a particular type of institution.
-
E.
hasFormerAffiliationOfLeader
Indicates that an entity was previously affiliated with the organization or group to which a specified leader once belonged or led.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:31 p.m.