Triple
T24464059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Street (Los Angeles) |
E616916
|
entity |
| Predicate | hasStreetLevelAccessTo |
P50259
|
FINISHED |
| Object | Pershing Square station |
—
|
NE NERFINISHED |
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: Pershing Square station | Statement: [Fourth Street (Los Angeles), hasStreetLevelAccessTo, Pershing Square station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetLevelAccessTo Context triple: [Fourth Street (Los Angeles), hasStreetLevelAccessTo, Pershing Square station]
-
A.
hasStreetLevel
chosen
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
B.
hasAccessRoadsTo
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
C.
hasValleyAccessTo
Indicates that one location can be reached from another specifically by traveling through a valley or valley-based route.
-
D.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cc60448190a5383d452f563834 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.