Triple
T6469076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warehouse 12 at Port of Beirut |
E142301
|
entity |
| Predicate | storedImproperly |
P3676
|
FINISHED |
| Object | ammonium nitrate |
—
|
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: ammonium nitrate | Statement: [Warehouse 12 at Port of Beirut, storedImproperly, ammonium nitrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storedImproperly Context triple: [Warehouse 12 at Port of Beirut, storedImproperly, ammonium nitrate]
-
A.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
B.
storageFacility
chosen
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
C.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
-
D.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
E.
impounds
Indicates the act of seizing and holding property, typically by an authority, so it is kept in custody and temporarily removed from the owner’s control.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a16272c81909313455002cd884d |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.