Triple
T8109673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploiești |
E189315
|
entity |
| Predicate | importanceToAllies |
P81332
|
FINISHED |
| Object | priority strategic bombing 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: priority strategic bombing target | Statement: [Ploiești, importanceToAllies, priority strategic bombing target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceToAllies Context triple: [Ploiești, importanceToAllies, priority strategic bombing target]
-
A.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
B.
aimOfAllies
Indicates that one entity represents the shared goal or objective pursued collectively by a group of allied entities.
-
C.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
-
D.
alliedRecognition
Indicates that one entity formally acknowledges another as an ally or partner in a cooperative relationship.
-
E.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:32 p.m.