Triple
T515224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2003 |
E10691
|
entity |
| Predicate | scoreWinner |
P7114
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [MLS Cup 2003, scoreWinner, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreWinner Context triple: [MLS Cup 2003, scoreWinner, 4]
-
A.
winnerPoints
chosen
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
B.
winnerCount
Indicates the number of entities that are designated as winners in a given context or event.
-
C.
positionOfWinner
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
D.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
E.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.