Triple
T26751545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 36 |
E674550
|
entity |
| Predicate | nearWesternTerminus |
P4246
|
FINISHED |
| Object | Fortuna, California |
—
|
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: Fortuna, California | Statement: [SR 36, nearWesternTerminus, Fortuna, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearWesternTerminus Context triple: [SR 36, nearWesternTerminus, Fortuna, California]
-
A.
westernTerminusNear
chosen
Indicates that the western endpoint of one entity is located close to another entity.
-
B.
terminusWestNear
Indicates that the western terminus of one entity is located near the western terminus of another entity.
-
C.
westernTerminusDetail
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
D.
terminusProvinceWest
Indicates that the western terminus of an entity (such as a route or line) is located within a specified province.
-
E.
westernTerminusConnectsTo
Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618898f788190b00fdf6a69d79900 |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:53 a.m.