Triple
T24541712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort of Exilles |
E607111
|
entity |
| Predicate | controlledPassage |
P63041
|
FINISHED |
| Object | route between Turin and Briançon |
—
|
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: route between Turin and Briançon | Statement: [Fort of Exilles, controlledPassage, route between Turin and Briançon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledPassage Context triple: [Fort of Exilles, controlledPassage, route between Turin and Briançon]
-
A.
guardedPassage
chosen
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
B.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
C.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.