Triple
T37696502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of the Princes for King George V in 1936 |
E938942
|
entity |
| Predicate | hasFutureMonarchParticipant |
P2434
|
FINISHED |
| Object | George VI |
—
|
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: George VI | Statement: [Vigil of the Princes for King George V in 1936, hasFutureMonarchParticipant, George VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFutureMonarchParticipant Context triple: [Vigil of the Princes for King George V in 1936, hasFutureMonarchParticipant, George VI]
-
A.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
hasPartyMember
Indicates that a particular individual is a member or participant of a specified party or group.
-
C.
hasFutureTimeline
Indicates that an entity is associated with a projected or planned sequence of events extending into the future.
-
D.
hasParticipantForce
Indicates that an event or action involves a participant specifically in the role of exerting or applying force.
-
E.
hasFormerParticipant
Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.