Triple
T486395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2001 |
E9887
|
entity |
| Predicate | titleForWinner |
P12322
|
FINISHED |
| Object | first MLS Cup title for San Jose Earthquakes |
—
|
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: first MLS Cup title for San Jose Earthquakes | Statement: [MLS Cup 2001, titleForWinner, first MLS Cup title for San Jose Earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleForWinner Context triple: [MLS Cup 2001, titleForWinner, first MLS Cup title for San Jose Earthquakes]
-
A.
wonDivisionTitle
Indicates that an entity secured first place in its competitive division, earning the division championship title.
-
B.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
C.
wonLeagueTitle
chosen
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
titleHeldIn
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bc6f548190b13dee42cb100423 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.