Triple
T27464844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied grand strategy in World War II |
E693150
|
entity |
| Predicate | implementedByBody |
P160957
|
FINISHED |
| Object | Allied joint planning staffs |
—
|
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: Allied joint planning staffs | Statement: [Allied grand strategy in World War II, implementedByBody, Allied joint planning staffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedByBody Context triple: [Allied grand strategy in World War II, implementedByBody, Allied joint planning staffs]
-
A.
implementationBody
chosen
Indicates that one entity serves as the concrete implementation or body that realizes, defines, or executes the behavior specified by another entity.
-
B.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
C.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
D.
alsoImplementedBy
Indicates that the same functionality, specification, or concept is realized or carried out by an additional implementation or agent beyond the primary one.
-
E.
currentlyImplementedBy
Indicates that a given specification, design, or feature is presently realized or supported by a particular implementation or system.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:51 p.m.