Triple
T27092602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeones Cup: Columbus Crew |
E686208
|
entity |
| Predicate | homeStadiumMLSClub |
P14307
|
FINISHED |
| Object | Lower.com Field |
—
|
NE NERFINISHED |
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: Lower.com Field | Statement: [Campeones Cup: Columbus Crew, homeStadiumMLSClub, Lower.com Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumMLSClub Context triple: [Campeones Cup: Columbus Crew, homeStadiumMLSClub, Lower.com Field]
-
A.
homeLeagueClub
Indicates that a club competes in or is affiliated with a particular home league.
-
B.
homeStadiumAlsoKnownAs
Indicates that an alternative or alias name is used for a stadium that serves as a team's home venue.
-
C.
homeStadiumSupportedTeam
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team.
-
D.
homeStadiumInvolved
Indicates that an event, action, or relationship involves a team's home stadium as a relevant location or context.
-
E.
parentClubStadium
Indicates that a stadium serves as the home venue associated with a particular parent club.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6234a6170819094a1f6d3a7864900 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:41 a.m.