Triple
T23465556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenge Tour |
E569092
|
entity |
| Predicate | hasFinalEventType |
P14526
|
FINISHED |
| Object | season-ending 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: season-ending championship | Statement: [Challenge Tour, hasFinalEventType, season-ending championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalEventType Context triple: [Challenge Tour, hasFinalEventType, season-ending championship]
-
A.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
B.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
C.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
D.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
-
E.
hasDeterminingEvent
Indicates that one event or occurrence serves as the decisive cause, condition, or basis that determines another situation, outcome, or state.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6faaf8c8190b4fd191c54e1acea |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.