Triple
T35713549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alameda del Valle |
E1031934
|
entity |
| Predicate | hasTransportModeAccess |
P37966
|
FINISHED |
| Object | road |
—
|
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: road | Statement: [Alameda del Valle, hasTransportModeAccess, road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportModeAccess Context triple: [Alameda del Valle, hasTransportModeAccess, road]
-
A.
transportModeAccess
chosen
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasTransportAuthority
Indicates that one entity holds official power or responsibility to manage, regulate, or oversee transportation services or infrastructure for another entity or area.
-
D.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
-
E.
hasTransportationAbove
Indicates that one entity provides or has transportation infrastructure or services located above another entity (e.g., elevated roads, railways, or transit lines).
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:05 p.m.