Triple
T26967433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Precourt Sports Ventures |
E679207
|
entity |
| Predicate | timeInControlOfColumbusCrew |
P161391
|
FINISHED |
| Object | 2013–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: 2013–2018 | Statement: [Precourt Sports Ventures, timeInControlOfColumbusCrew, 2013–2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInControlOfColumbusCrew Context triple: [Precourt Sports Ventures, timeInControlOfColumbusCrew, 2013–2018]
-
A.
MLS CupFinalCity
Indicates the city where the MLS Cup final match is held.
-
B.
PhiladelphiaUnionFirstFinalAppearance
Indicates that the Philadelphia Union soccer club is making its first-ever appearance in a final match or championship game.
-
C.
losingTeamFinalAppearancesCountForNewEnglandRevolution
Indicates the number of times the New England Revolution appeared in a final and ended up as the losing team.
-
D.
eligibleForUSOpenCup
Indicates that an entity (typically a soccer club or team) meets the criteria to participate in the U.S. Open Cup competition.
-
E.
inauguralMLSMatchResult
Indicates the outcome or result of an entity’s first-ever match in Major League Soccer.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621222ea88190a58d686d3b4cc802 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:36 a.m.