Triple
T5396456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort de Joux |
E120667
|
entity |
| Predicate | regionHistory |
P63734
|
FINISHED |
| Object | part of Franche-Comté defensive system |
—
|
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: part of Franche-Comté defensive system | Statement: [Fort de Joux, regionHistory, part of Franche-Comté defensive system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHistory Context triple: [Fort de Joux, regionHistory, part of Franche-Comté defensive system]
-
A.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
C.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
D.
historicalCoreRegion
Indicates that a region served as the central or foundational area of a group, state, or civilization during a significant historical period.
-
E.
formsHistoricalRegionWith
Indicates that two or more entities together constitute or are recognized as a single historical region.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8931302c81908afcb0f011e91f09 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:04 p.m.