Triple
T24560206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Greif |
E607627
|
entity |
| Predicate | plannedStrength |
P156329
|
FINISHED |
| Object | Panzerbrigade 150 disguised as Allied troops |
—
|
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: Panzerbrigade 150 disguised as Allied troops | Statement: [Operation Greif, plannedStrength, Panzerbrigade 150 disguised as Allied troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedStrength Context triple: [Operation Greif, plannedStrength, Panzerbrigade 150 disguised as Allied troops]
-
A.
initialStrength
Indicates the original or starting level of strength associated with an entity before any changes or influences occur.
-
B.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
C.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
-
D.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f57a7c8190a0eb8d6d6ef6ae61 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.