Triple
T37309204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Caesar Augusta |
E926157
|
entity |
| Predicate | hadRoadConnection |
P51093
|
FINISHED |
| Object | Roman road network in Hispania |
—
|
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: Roman road network in Hispania | Statement: [Colonia Caesar Augusta, hadRoadConnection, Roman road network in Hispania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRoadConnection Context triple: [Colonia Caesar Augusta, hadRoadConnection, Roman road network in Hispania]
-
A.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
D.
hasRoadway
chosen
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.