Triple
T24202790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheamus |
E600023
|
entity |
| Predicate | multiTimeWorldChampion |
P99897
|
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: [Sheamus, multiTimeWorldChampion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiTimeWorldChampion Context triple: [Sheamus, multiTimeWorldChampion, true]
-
A.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
-
B.
hasProducedWorldChampions
Indicates that an entity has been responsible for training, developing, or otherwise producing individuals or teams that have won a recognized world championship.
-
C.
hasWonMultipleChampionships
chosen
Indicates that the subject has secured championship titles on more than one separate occasion.
-
D.
worldChampionIn
Indicates that an entity holds or has held the title of world champion in a specified field, discipline, or competition.
-
E.
worldChampionPredecessor
Indicates that one entity was the immediate previous world champion before another entity.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca2d6708190ba20d00870d0af49 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.