Triple
T2625977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Cincinnati |
E59117
|
entity |
| Predicate | foundedAsMLSClub |
P34649
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [FC Cincinnati, foundedAsMLSClub, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsMLSClub Context triple: [FC Cincinnati, foundedAsMLSClub, 2018]
-
A.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
B.
foundedAsMajorLeagueClub
chosen
Indicates that an organization or team was originally established as a major league club at the time of its founding.
-
C.
originalMLSClub
Indicates the Major League Soccer club with which an entity (typically a player) was first officially associated or began their MLS career.
-
D.
foundedAsNationalTeam
Indicates that an organization or team was originally established as a national team representing a country.
-
E.
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.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.