Triple
T8646268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Labour Party leadership election |
E204984
|
entity |
| Predicate | resultAnnouncedAt |
P430
|
FINISHED |
| Object | special conference in London |
—
|
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: special conference in London | Statement: [2015 Labour Party leadership election, resultAnnouncedAt, special conference in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAnnouncedAt Context triple: [2015 Labour Party leadership election, resultAnnouncedAt, special conference in London]
-
A.
announcedAt
chosen
Indicates that an announcement or declaration was made at a specific time or event.
-
B.
announcedAfter
Indicates that one announcement occurred later in time than another specified announcement.
-
C.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
-
D.
voteResultAnnouncementDate
Indicates the date on which the outcome of a vote is officially announced.
-
E.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc480eb7f88190a38d2150976cd47f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.