Triple
T6123231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Major League Soccer season |
E136531
|
entity |
| Predicate | usesConferenceSystem |
P47976
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2004 Major League Soccer season, usesConferenceSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConferenceSystem Context triple: [2004 Major League Soccer season, usesConferenceSystem, true]
-
A.
hasConferenceSystem
chosen
Indicates that an entity is equipped with or utilizes a particular conference or conferencing system.
-
B.
usesConferenceStructure
Indicates that one entity organizes, presents, or operates another entity according to a conference-style structure or format.
-
C.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
D.
associatedWithConference
Indicates that an entity has a connection or involvement with a specific conference, such as participation, organization, or affiliation.
-
E.
isPowerConference
Indicates that an athletic conference is considered a major or elite "power" conference within its sport or league.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c247b7081909972b40afb165e6f |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.