Triple
T34287918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orphans |
E879792
|
entity |
| Predicate | predecessorTeamOf |
P194776
|
FINISHED |
| Object | modern Chicago Cubs |
—
|
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: modern Chicago Cubs | Statement: [Orphans, predecessorTeamOf, modern Chicago Cubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTeamOf Context triple: [Orphans, predecessorTeamOf, modern Chicago Cubs]
-
A.
predecessorTeamContext
Indicates that one team context directly precedes another in a sequence or timeline of team configurations or states.
-
B.
hasSuccessorTeam
Indicates that one team is the direct successor or continuation of another team, typically following rebranding, relocation, or organizational change.
-
C.
successorTeamInception
Indicates that one team was formed as the direct successor to another team at the time of its inception.
-
D.
predecessorManagedBy
Indicates that a predecessor entity was managed, overseen, or administered by another entity.
-
E.
teamPredecessorCity
Indicates that one sports team previously based in a given city is the predecessor or earlier incarnation of another team in that city.
- F. None of above. chosen
Provenance (4 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: May 1, 2026, 1:57 a.m.