Triple
T8581458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde, California |
E203188
|
entity |
| Predicate | distanceToConcord |
P82960
|
FINISHED |
| Object | approximately 2.5 miles north of downtown Concord |
—
|
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 2.5 miles north of downtown Concord | Statement: [Clyde, California, distanceToConcord, approximately 2.5 miles north of downtown Concord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToConcord Context triple: [Clyde, California, distanceToConcord, approximately 2.5 miles north of downtown Concord]
-
A.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
-
C.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
-
D.
distanceToSpringfield
Indicates the measured distance between a given location and the place named Springfield.
-
E.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1bbbd8819082670286a711826d |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:22 p.m.