Triple
T7427459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 Major League Soccer season |
E171403
|
entity |
| Predicate | conferenceFinalsFormat |
P30656
|
FINISHED |
| Object | single match |
—
|
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: single match | Statement: [2005 Major League Soccer season, conferenceFinalsFormat, single match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceFinalsFormat Context triple: [2005 Major League Soccer season, conferenceFinalsFormat, single match]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
semiFinalFormat
Indicates the structure or rules used to organize and play the semifinal stage of a competition or tournament.
-
C.
worldCupFormat
Indicates the specific structure, rules, and progression system used to organize and play a given World Cup competition.
-
D.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
E.
finalMatchType
chosen
Indicates the specific category or format of the concluding or decisive match in a series or competition.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3055b7881908269ab909c5a85b5 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.