Triple
T8313105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgica Prima |
E194637
|
entity |
| Predicate | hadRoadNetwork |
P74765
|
FINISHED |
| Object | Roman roads |
—
|
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 roads | Statement: [Belgica Prima, hadRoadNetwork, Roman roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRoadNetwork Context triple: [Belgica Prima, hadRoadNetwork, Roman roads]
-
A.
hasRoadNetworkType
chosen
Indicates the type or classification of road network associated with or present in an entity.
-
B.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
C.
hasRoadNetworkQuality
Indicates the assessed level or condition of the road network associated with an entity.
-
D.
hasCountyRoad
Indicates that one place or administrative area is connected to or served by a designated county-maintained road.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f5173c881909f2e84d53ea33a98 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.