Triple
T24635330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss United Kingdom |
E609795
|
entity |
| Predicate | historicallySentWinnersTo |
P156856
|
FINISHED |
| Object | Miss World |
—
|
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: Miss World | Statement: [Miss United Kingdom, historicallySentWinnersTo, Miss World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallySentWinnersTo Context triple: [Miss United Kingdom, historicallySentWinnersTo, Miss World]
-
A.
recordWinners
Indicates that an entity documents or stores information about the winners of a particular event, contest, or competition.
-
B.
fieldOfWinners
Indicates that a given field or domain is associated with the winners of a particular competition, award, or event.
-
C.
positionOfTypicalWinners
Indicates the usual or most common placement or ranking that winners occupy in a given context or competition.
-
D.
historicallyGivenTo
Indicates that something was transferred or bestowed upon an entity at some point in the past, typically as recorded or recognized in historical accounts.
-
E.
winnerPreviouslyWon
Indicates that the winner has won the same or a related contest/event at least once before.
- F. None of above. chosen
Provenance (4 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.