Triple
T16116686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploiești oil fields |
E391017
|
entity |
| Predicate | militaryTargetType |
P81775
|
FINISHED |
| Object | strategic industrial target |
—
|
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: strategic industrial target | Statement: [Ploiești oil fields, militaryTargetType, strategic industrial target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryTargetType Context triple: [Ploiești oil fields, militaryTargetType, strategic industrial target]
-
A.
civilianTarget
Indicates that the action or operation is directed at, affects, or designates civilians or civilian objects as the target.
-
B.
enemyTechnologyTargeted
Indicates that a technology belonging to an enemy is being specifically selected or targeted for attack, disruption, or counteraction.
-
C.
hasMilitaryType
chosen
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
targetedAircraft
Indicates that one entity has selected or designated an aircraft as the object of an attack, tracking, or other directed action.
-
E.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016b5c948190b0f1eccb97ee85cc |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.