Triple
T30826081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herlong |
E785066
|
entity |
| Predicate | distanceToSusanville |
P203332
|
FINISHED |
| Object | about 43 miles southeast |
—
|
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: about 43 miles southeast | Statement: [Herlong, distanceToSusanville, about 43 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSusanville Context triple: [Herlong, distanceToSusanville, about 43 miles southeast]
-
A.
distanceFromSacramento
Indicates the measured distance between a given location and the city of Sacramento.
-
B.
distanceToVisalia
Indicates the spatial distance between a given entity and the location of Visalia.
-
C.
distanceToTurlock
Indicates the spatial distance between a given location or entity and the place named Turlock.
-
D.
distanceFromSanJosé
Indicates the measured spatial distance between a given entity and the location of San José.
-
E.
distanceFromReno
Indicates the spatial distance between a given entity and the location Reno.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
| PDg | Predicate description generation | batch_6a016082388081908a037b8427f6f99d |
completed | May 11, 2026, 4:52 a.m. |
Created at: April 29, 2026, 8:44 p.m.