Triple
T32292990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hackenberg hill |
E825015
|
entity |
| Predicate | associatedMilitaryStructure |
P120787
|
FINISHED |
| Object | Ouvrage Hackenberg |
E239503
|
NE 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: Ouvrage Hackenberg | Statement: [Hackenberg hill, associatedMilitaryStructure, Ouvrage Hackenberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMilitaryStructure Context triple: [Hackenberg hill, associatedMilitaryStructure, Ouvrage Hackenberg]
-
A.
partOfMilitaryStructure
chosen
Indicates that one entity is a component, unit, or subdivision within the organizational hierarchy of a military structure.
-
B.
armedStructure
Indicates that a structure is equipped with weapons or defensive armaments.
-
C.
militaryArchitecture
Indicates a relationship where something is designed, built, or characterized specifically for military defensive or fortification purposes.
-
D.
shareDefenseStructure
Indicates that two or more entities utilize or are protected by the same defensive structure or system.
-
E.
garrisonOrTheater
Indicates that one entity serves as a military garrison or theater of operations for another entity.
- F. None of above.
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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a305706cb78819088a3cd05e5b2588c |
completed | June 15, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:44 a.m.