Triple
T451250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | funeral of Queen Elizabeth II |
E7132
|
entity |
| Predicate | planningDuration |
P11255
|
FINISHED |
| Object | planned for many years before 2022 |
—
|
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: planned for many years before 2022 | Statement: [funeral of Queen Elizabeth II, planningDuration, planned for many years before 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningDuration Context triple: [funeral of Queen Elizabeth II, planningDuration, planned for many years before 2022]
-
A.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
B.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
planned
chosen
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
E.
planner
Indicates that an entity is responsible for organizing, scheduling, or coordinating activities, tasks, or resources.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef835ae881908884dcc3a46af951 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.