Triple
T6064352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burdigala |
E135117
|
entity |
| Predicate | hasRomanRoadConnection |
P47630
|
FINISHED |
| Object | Via leading to Mediolanum Santonum (Saintes) |
—
|
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: Via leading to Mediolanum Santonum (Saintes) | Statement: [Burdigala, hasRomanRoadConnection, Via leading to Mediolanum Santonum (Saintes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanRoadConnection Context triple: [Burdigala, hasRomanRoadConnection, Via leading to Mediolanum Santonum (Saintes)]
-
A.
romanRoad
chosen
Indicates that one location is connected to another by a road constructed or used during the Roman period.
-
B.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
C.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
D.
hasVoivodeshipRoad
Indicates that an entity is connected to or served by a specific voivodeship (regional) road.
-
E.
wasRomanTown
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.