Triple
T30880790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Félix Cuevas |
E786605
|
entity |
| Predicate | locatedOnCorridorType |
P26881
|
FINISHED |
| Object | north–south 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: north–south corridor | Statement: [Félix Cuevas, locatedOnCorridorType, north–south corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnCorridorType Context triple: [Félix Cuevas, locatedOnCorridorType, north–south corridor]
-
A.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
corridorStatus
Indicates the current operational or accessibility state of a corridor (e.g., open, closed, restricted, or otherwise constrained).
-
E.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
Created at: April 29, 2026, 8:48 p.m.