Triple
T32242927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frazier Park, California |
E823665
|
entity |
| Predicate | distanceToInterstate5 |
P204208
|
FINISHED |
| Object | approximately 5 miles |
—
|
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: approximately 5 miles | Statement: [Frazier Park, California, distanceToInterstate5, approximately 5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToInterstate5 Context triple: [Frazier Park, California, distanceToInterstate5, approximately 5 miles]
-
A.
distanceToCaliforniaBorder
Indicates the measured or specified distance between a given location and the border of the state of California.
-
B.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
C.
distanceFromLosAngeles
Indicates the measured or specified distance between a given entity’s location and the city of Los Angeles.
-
D.
exitNumberOnInterstate5
Indicates the specific exit number assigned to a location along Interstate 5.
-
E.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
- 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_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_6a0349d09ba88190918a4205de46638f |
completed | May 12, 2026, 3:40 p.m. |
Created at: May 1, 2026, 12:40 a.m.