Triple
T8311180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isauria |
E194592
|
entity |
| Predicate | romanRoadNetwork |
P3293
|
FINISHED |
| Object | connected to Cilicia and Lycaonia |
—
|
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: connected to Cilicia and Lycaonia | Statement: [Isauria, romanRoadNetwork, connected to Cilicia and Lycaonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanRoadNetwork Context triple: [Isauria, romanRoadNetwork, connected to Cilicia and Lycaonia]
-
A.
romanRoad
Indicates that one location is connected to another by a road constructed or used during the Roman period.
-
B.
roadSystem
chosen
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
E.
hasVoivodeshipRoad
Indicates that an entity is connected to or served by a specific voivodeship (regional) road.
- 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_69cb7f2eecb08190ae0ba8adbaf58c8f |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.