Triple
T7079492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 121 |
E164909
|
entity |
| Predicate | terminusSouthLocation |
P29526
|
FINISHED |
| Object | near Sears Point |
—
|
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: near Sears Point | Statement: [California State Route 121, terminusSouthLocation, near Sears Point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusSouthLocation Context triple: [California State Route 121, terminusSouthLocation, near Sears Point]
-
A.
terminusSouthNear
chosen
Indicates that the southern end or terminus of one entity is located close to another entity.
-
B.
terminusSouthCountry
Indicates that the southern terminus of a route, line, or connection is located within the specified country.
-
C.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
D.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ef47d48190b31125d1b57f7bec |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.