Triple
T32552854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zion |
E832018
|
entity |
| Predicate | defenseEvent |
P35255
|
FINISHED |
| Object | Battle of Zion |
—
|
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 Zion | Statement: [Zion, defenseEvent, Battle of Zion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseEvent Context triple: [Zion, defenseEvent, Battle of Zion]
-
A.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
B.
defense
chosen
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
C.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
-
D.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
E.
defenseArea
Indicates a spatial region or zone that is designated for defensive protection or military/security defense activities.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:02 a.m.