Triple
T30807917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostian Road |
E784555
|
entity |
| Predicate | hasUrbanTerminus |
P171096
|
FINISHED |
| Object | Rome |
—
|
NE NERFINISHED |
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: Rome | Statement: [Ostian Road, hasUrbanTerminus, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanTerminus Context triple: [Ostian Road, hasUrbanTerminus, Rome]
-
A.
hasSuburbanTerminus
Indicates that a transportation route or service ends at a terminus located in a suburban area.
-
B.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
-
C.
hasUrbanAccess
Indicates that an entity has access to urban areas, services, or infrastructure.
-
D.
hasUrbanSectionsIn
Indicates that an entity includes or contains sections that are classified as urban within a specified area or region.
-
E.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
- F. None of above. chosen
Provenance (4 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:43 p.m.