Triple
T25589161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoPac Trail |
E641471
|
entity |
| Predicate | hasTransportationCorridorOrigin |
P170935
|
FINISHED |
| Object | railroad |
—
|
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: railroad | Statement: [SoPac Trail, hasTransportationCorridorOrigin, railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportationCorridorOrigin Context triple: [SoPac Trail, hasTransportationCorridorOrigin, railroad]
-
A.
isGatewayCorridorFor
Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
-
B.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
hasNearbyTransportationCorridor
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
-
E.
partOfTransportCorridorTo
Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 21, 2026, 4:18 p.m.