Triple
T37696490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of the Princes for King George V in 1936 |
E938942
|
entity |
| Predicate | hasCoffinLocation |
P40790
|
FINISHED |
| Object | lying in state |
—
|
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: lying in state | Statement: [Vigil of the Princes for King George V in 1936, hasCoffinLocation, lying in state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoffinLocation Context triple: [Vigil of the Princes for King George V in 1936, hasCoffinLocation, lying in state]
-
A.
coffinLocation
chosen
Indicates the place where a coffin is situated or stored.
-
B.
hasTombChapel
Indicates that an entity possesses or is associated with a specific tomb chapel as part of its funerary or commemorative context.
-
C.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
D.
hasPartInGrave
Indicates that an entity includes another entity as a physical component or element within a grave.
-
E.
hasGraveOccupant
Indicates that a grave is occupied by a specific person or 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.