Triple
T22989871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Major League Soccer season |
E572015
|
entity |
| Predicate | featuredCompetitionFor |
P150533
|
FINISHED |
| Object | league championship |
—
|
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: league championship | Statement: [2003 Major League Soccer season, featuredCompetitionFor, league championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCompetitionFor Context triple: [2003 Major League Soccer season, featuredCompetitionFor, league championship]
-
A.
featuredCompetition
Indicates that a particular competition is highlighted or given special prominence relative to others.
-
B.
featuredCompetitionLevel
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
-
C.
featuredInCompetition
Indicates that an entity was included or showcased as a participant or entry in a specific competition.
-
D.
featuresCompetitionIn
Indicates that something includes or presents a particular competition as part of its content or structure.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182ea55cc8190b64b722ce8c45b53 |
completed | April 29, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.