Triple
T31739157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centro Histórico–Buenavista corridor |
E810084
|
entity |
| Predicate | roadTransportType |
P56025
|
FINISHED |
| Object | surface transit corridor |
—
|
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: surface transit corridor | Statement: [Centro Histórico–Buenavista corridor, roadTransportType, surface transit corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTransportType Context triple: [Centro Histórico–Buenavista corridor, roadTransportType, surface transit corridor]
-
A.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
-
B.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
typeOfTransportInfrastructure
chosen
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
D.
primaryTransports
Indicates that one entity serves as the main means or method of transporting or conveying another entity.
-
E.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab25d0748190adccdc5fbbfe4902 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:24 p.m.