Triple
T37696517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of the Princes for King George V in 1936 |
E938942
|
entity |
| Predicate | hasBodyHonoured |
P197434
|
FINISHED |
| Object | coffin of King George V |
—
|
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: coffin of King George V | Statement: [Vigil of the Princes for King George V in 1936, hasBodyHonoured, coffin of King George V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyHonoured Context triple: [Vigil of the Princes for King George V in 1936, hasBodyHonoured, coffin of King George V]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
hasBodyStatus
Indicates the physical or health condition currently associated with a body or bodily entity.
-
D.
hasBodyCount
Indicates that an entity is associated with a specific number of deaths or kills.
-
E.
allowsBodyChecking
Indicates that one party permits physical body checking to be used against another in a competitive or contact context.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 3, 2026, 4:18 p.m.