Triple
T37535252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secteur fortifié de Modane |
E933176
|
entity |
| Predicate | borderDefenseType |
P201613
|
FINISHED |
| Object | fixed fortification line |
—
|
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: fixed fortification line | Statement: [Secteur fortifié de Modane, borderDefenseType, fixed fortification line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDefenseType Context triple: [Secteur fortifié de Modane, borderDefenseType, fixed fortification line]
-
A.
sharesBorderDefenseWith
Indicates that two entities cooperate or coordinate in protecting and defending their shared border.
-
B.
featuresDefenseBy
Indicates that an entity possesses or is characterized by a defense mechanism, strategy, or protective feature provided or implemented by another entity.
-
C.
shipDefenseType
Indicates the specific kind of defensive system or protection mechanism that a ship employs.
-
D.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
E.
coastalDefense
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_6a000be4d3f48190bdecd0a044a0e453 |
completed | May 10, 2026, 4:39 a.m. |
Created at: May 3, 2026, 4:17 p.m.