Triple
T25001428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperBrawl |
E625728
|
entity |
| Predicate | finalEventYear |
P214
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [SuperBrawl, finalEventYear, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalEventYear Context triple: [SuperBrawl, finalEventYear, 2001]
-
A.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
B.
finalPerformanceYear
Indicates the year in which an entity’s performance or activity is recorded or recognized for the last time.
-
C.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
-
D.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
E.
conclusionYear
Indicates the year in which something (such as an event, project, or period) comes to an end or is completed.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:04 a.m.