Triple
T26746431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Station, San Diego, California |
E674413
|
entity |
| Predicate | hasPrimaryStreetAccess |
P108870
|
FINISHED |
| Object | Rosecrans Street |
—
|
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: Rosecrans Street | Statement: [Liberty Station, San Diego, California, hasPrimaryStreetAccess, Rosecrans Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStreetAccess Context triple: [Liberty Station, San Diego, California, hasPrimaryStreetAccess, Rosecrans Street]
-
A.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
B.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
-
C.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
-
D.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
E.
isOnlyMajorRoadAccessTo
chosen
Indicates that one road is the sole major roadway providing access to a particular place or area.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 27, 2026, 3:51 a.m.