Triple
T28141393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hostilia |
E714350
|
entity |
| Predicate | roadNetworkRelation |
P122298
|
FINISHED |
| Object | gateway to Alpine passes |
—
|
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: gateway to Alpine passes | Statement: [Hostilia, roadNetworkRelation, gateway to Alpine passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkRelation Context triple: [Hostilia, roadNetworkRelation, gateway to Alpine passes]
-
A.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
B.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
C.
cityInfrastructureRelation
chosen
Indicates a relationship between a city and elements of its infrastructure, such as facilities, networks, or services that support its functioning.
-
D.
roadDistanceRelation
Indicates a relationship specifying the distance between two locations as measured along a road or road network.
-
E.
roadAssociatedWith
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:53 p.m.