Triple
T11103898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Augustus (Rimini) |
E262577
|
entity |
| Predicate | associatedWithRoadNetwork |
P30193
|
FINISHED |
| Object | Roman road system |
—
|
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 system | Statement: [Arch of Augustus (Rimini), associatedWithRoadNetwork, Roman road system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoadNetwork Context triple: [Arch of Augustus (Rimini), associatedWithRoadNetwork, Roman road system]
-
A.
associatedWithRouteNetwork
chosen
Indicates a relationship where something is linked or connected to a specific route network.
-
B.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
C.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
D.
roadNetworkServedBy
Indicates that a particular road network is provided, maintained, or operated by a specified service, organization, or infrastructure system.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2d33948190ac29d174694a78e5 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.