Triple
T11202466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadows |
E265072
|
entity |
| Predicate | laterBlownUpTo |
P97837
|
FINISHED |
| Object | 35 mm film |
—
|
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: 35 mm film | Statement: [Shadows, laterBlownUpTo, 35 mm film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBlownUpTo Context triple: [Shadows, laterBlownUpTo, 35 mm film]
-
A.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
B.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
C.
detonatedBy
Indicates that an explosive or device is set off or caused to explode by a particular agent or entity.
-
D.
explosionDateApprox
Indicates that an explosion occurred on or around a specified date, where the exact date is not known or is only approximate.
-
E.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c36c188190bfa4d5f8e6cbbbea |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.