Triple
T28141481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finstermünz |
E714352
|
entity |
| Predicate | historicalRoadConnection |
P192563
|
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: [Finstermünz, historicalRoadConnection, Via Claudia Augusta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRoadConnection Context triple: [Finstermünz, historicalRoadConnection, Via Claudia Augusta]
-
A.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
B.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
C.
hasHistoricTransportLink
chosen
Indicates that there is or was a historically significant transportation connection between the related entities.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
transportRouteInAntiquity
Indicates that there existed a transportation route between entities during ancient or classical historical periods.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 27, 2026, 9:53 p.m.