Triple
T29480531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Labour Party leadership election |
E747770
|
entity |
| Predicate | locationOfResultAnnouncement |
P3059
|
FINISHED |
| Object | Liverpool |
—
|
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: Liverpool | Statement: [2016 Labour Party leadership election, locationOfResultAnnouncement, Liverpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfResultAnnouncement Context triple: [2016 Labour Party leadership election, locationOfResultAnnouncement, Liverpool]
-
A.
announcementLocation
chosen
Indicates the place or venue where an announcement is made or presented.
-
B.
resultAnnouncementBody
Indicates the textual content used to announce or communicate the outcome or result of an event, process, or evaluation.
-
C.
locationOfBroadcast
Indicates the place or geographic area from which a broadcast is transmitted or originates.
-
D.
discoveryAnnouncementBy
Indicates that a particular entity publicly announces or reports the discovery of another entity or finding.
-
E.
positionOfAnnouncer
Indicates the spatial location or placement of the announcer relative to other relevant entities or context.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: April 28, 2026, 4:03 p.m.