Triple
T32170934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornburg |
E821706
|
entity |
| Predicate | filmDepictionBattle |
P39393
|
FINISHED |
| Object | Battle of Helm's Deep (film adaptation) |
—
|
NE NERFINISHED |
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: Battle of Helm's Deep (film adaptation) | Statement: [Hornburg, filmDepictionBattle, Battle of Helm's Deep (film adaptation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmDepictionBattle Context triple: [Hornburg, filmDepictionBattle, Battle of Helm's Deep (film adaptation)]
-
A.
battleDepicted
chosen
Indicates that a work or representation visually portrays a specific battle or combat event.
-
B.
warDepicted
Indicates that a work or representation portrays, illustrates, or otherwise depicts a particular war or armed conflict.
-
C.
hasBattleScenes
Indicates that an entity (such as a work of fiction or media) contains scenes depicting battles or combat.
-
D.
depictsWarAs
Indicates that one entity portrays or represents war in a particular way or light.
-
E.
battleRelatedTo
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:33 a.m.