Triple
T11951693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Cincinnati |
E284439
|
entity |
| Predicate | joinedMLSBy |
P18820
|
FINISHED |
| Object | expansion franchise |
—
|
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: expansion franchise | Statement: [FC Cincinnati, joinedMLSBy, expansion franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedMLSBy Context triple: [FC Cincinnati, joinedMLSBy, expansion franchise]
-
A.
joinedMLS
chosen
Indicates that an entity became a member of, or was admitted into, Major League Soccer (MLS).
-
B.
playedForMLSClub
Indicates that a person has been a player on the roster of a club that competes in Major League Soccer (MLS).
-
C.
rejoinedMLSAsExpansionTeam
Indicates that an entity returned to Major League Soccer by joining a team that entered the league as an expansion franchise.
-
D.
inauguralMLSMatchOpponent
Indicates the opposing team that a given team faced in its first-ever Major League Soccer (MLS) match.
-
E.
awayTeamPreviousMLS CupFinalAppearances
Indicates the number of times the away team has previously appeared in an MLS Cup final before the current match.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90364c2608190a3946c9595c71164 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.