Triple
T2552377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lying-in-state of Elizabeth II |
E56654
|
entity |
| Predicate | queueLocation |
P40792
|
FINISHED |
| Object | along the River Thames in central 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: along the River Thames in central London | Statement: [lying-in-state of Elizabeth II, queueLocation, along the River Thames in central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueLocation Context triple: [lying-in-state of Elizabeth II, queueLocation, along the River Thames in central London]
-
A.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
B.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
C.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
D.
barrageLocation
Indicates the location where a barrage (such as an artillery or concentrated attack) is directed or occurs.
-
E.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:48 p.m.