Triple
T15298160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancho Santa Fe, California |
E365713
|
entity |
| Predicate | distanceToPacificOceanInMiles |
P14280
|
FINISHED |
| Object | approximately 4–6 |
—
|
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 4–6 | Statement: [Rancho Santa Fe, California, distanceToPacificOceanInMiles, approximately 4–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPacificOceanInMiles Context triple: [Rancho Santa Fe, California, distanceToPacificOceanInMiles, approximately 4–6]
-
A.
distanceToPacificOcean
chosen
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
B.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
C.
distanceFromMainland
Indicates the measured spatial separation between a location and the nearest point on the mainland.
-
D.
distanceToGulfOfMexico
Indicates the measured or estimated spatial distance between a given location and the Gulf of Mexico.
-
E.
distanceFromHawaii
Indicates the measured spatial distance between a given entity and the location of Hawaii.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03686bfb8819080ba0caae652170a |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.