Triple
T32312729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenner Pass |
E825543
|
entity |
| Predicate | historicalRouteOn |
P139623
|
FINISHED |
| Object | Via Claudia Augusta |
—
|
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: Via Claudia Augusta | Statement: [Brenner Pass, historicalRouteOn, Via Claudia Augusta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRouteOn Context triple: [Brenner Pass, historicalRouteOn, Via Claudia Augusta]
-
A.
historicalRouteVia
chosen
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
B.
historicalRouteName
Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
-
C.
nearHistoricalRoute
Indicates that one entity is located close to a historically significant route or pathway.
-
D.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
E.
historicalRouteNumberOf
Indicates that one route number was previously used to designate the same route or segment as another, but is no longer its current official number.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 1, 2026, 12:46 a.m.