Triple
T33799011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss World 1967 |
E866158
|
entity |
| Predicate | winnerSuccessor |
P78
|
FINISHED |
| Object | Penelope Plummer |
—
|
NE NERFINISHED |
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: Penelope Plummer | Statement: [Miss World 1967, winnerSuccessor, Penelope Plummer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerSuccessor Context triple: [Miss World 1967, winnerSuccessor, Penelope Plummer]
-
A.
winnerWith
Indicates that one entity is the winner in a context or event specifically in association or combination with another entity.
-
B.
winnerRight
Indicates that the referenced entity is the winner on the right side or right position in a competitive or comparative context.
-
C.
winnerAssociated
Indicates that there is a relevant connection or affiliation between a winner and another entity in the context of a particular event or competition.
-
D.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
E.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:46 a.m.