Triple
T2911550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jericho-Trompete siren |
E63692
|
entity |
| Predicate | operationalPhase |
P8100
|
FINISHED |
| Object | dive-bombing attack |
—
|
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: dive-bombing attack | Statement: [Jericho-Trompete siren, operationalPhase, dive-bombing attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalPhase Context triple: [Jericho-Trompete siren, operationalPhase, dive-bombing attack]
-
A.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
B.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
C.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
D.
currentMissionPhase
chosen
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
E.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.