Triple
T31264570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führerhauptquartiere |
E797216
|
entity |
| Predicate | planningOf |
P72243
|
FINISHED |
| Object | Operation Barbarossa |
—
|
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: Operation Barbarossa | Statement: [Führerhauptquartiere, planningOf, Operation Barbarossa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningOf Context triple: [Führerhauptquartiere, planningOf, Operation Barbarossa]
-
A.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
B.
planningSkill
Indicates the degree to which an entity is capable of effectively organizing, sequencing, and coordinating actions or resources to achieve goals.
-
C.
planningProcess
chosen
Indicates a relationship where an entity is engaged in or associated with the structured activity of defining goals, strategies, and steps to achieve a desired outcome.
-
D.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 9:12 p.m.