Triple
T28382210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litvinenko inquiry in the United Kingdom |
E718916
|
entity |
| Predicate | cityOfInquiryHearings |
P166219
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [Litvinenko inquiry in the United Kingdom, cityOfInquiryHearings, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfInquiryHearings Context triple: [Litvinenko inquiry in the United Kingdom, cityOfInquiryHearings, London]
-
A.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
councilHeldHere
Indicates that a council or formal assembly took place at the specified location.
-
C.
allowsPublicHearings
Indicates that an entity permits public hearings to be held, allowing members of the public to attend and/or participate.
-
D.
courtHeld
Indicates that a court has formally decided, ruled, or determined a particular legal issue or question.
-
E.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 1:07 a.m.