Triple
T32242903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frazier Park, California |
E823665
|
entity |
| Predicate | nearestMajorPass |
P179956
|
FINISHED |
| Object | Tejon Pass |
—
|
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: Tejon Pass | Statement: [Frazier Park, California, nearestMajorPass, Tejon Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorPass Context triple: [Frazier Park, California, nearestMajorPass, Tejon Pass]
-
A.
nearestMajorNeighbor
Indicates that one entity is the closest significant or major neighboring entity to another in terms of spatial proximity.
-
B.
nearestMajorBase
Indicates that one location is the closest significant (major) base relative to another location.
-
C.
nearestMajorArea
Indicates the relationship where a given location is associated with the closest significant geographic or administrative area.
-
D.
nearestMajorPort
Indicates the closest significant seaport to a given location or entity, typically based on geographic distance.
-
E.
nearestPass
Indicates that one entity is the closest in distance or proximity to another entity compared to all other possible entities or paths.
- F. None of above. chosen
Provenance (4 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: May 1, 2026, 12:40 a.m.