Triple
T37696496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of the Princes for King George V in 1936 |
E938942
|
entity |
| Predicate | hasGuardForm |
P189147
|
FINISHED |
| Object | standing guard around the coffin |
—
|
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: standing guard around the coffin | Statement: [Vigil of the Princes for King George V in 1936, hasGuardForm, standing guard around the coffin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuardForm Context triple: [Vigil of the Princes for King George V in 1936, hasGuardForm, standing guard around the coffin]
-
A.
hasGuardUnit
Indicates that an entity is protected or overseen by a specific guard unit.
-
B.
hasGuardCharacter
Indicates that one entity serves as a guard or protective character for another entity.
-
C.
hasGovernanceForm
Indicates that an entity is organized or administered according to a particular system or form of governance.
-
D.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
E.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.