Triple
T5193181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianapolis ABCs |
E117204
|
entity |
| Predicate | charterLeagueFormationYear |
P55053
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Indianapolis ABCs, charterLeagueFormationYear, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterLeagueFormationYear Context triple: [Indianapolis ABCs, charterLeagueFormationYear, 1920]
-
A.
establishedInLeague
Indicates that an entity (such as a team or club) was founded or formally created while participating in, or as part of, a particular league.
-
B.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
C.
charterDate
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
D.
leagueFounded
chosen
Indicates that a particular sports league was established or came into existence on a specific date or in a specific year.
-
E.
teamFoundedLegacy
Indicates that a team was established as a continuation, successor, or legacy of a prior organization or team.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79efd16c8190b0b16278a00baecd |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.