Triple
T3753069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronxville, New York |
E81377
|
entity |
| Predicate | distanceToManhattanApprox |
P37106
|
FINISHED |
| Object | 15 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: 15 miles | Statement: [Bronxville, New York, distanceToManhattanApprox, 15 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToManhattanApprox Context triple: [Bronxville, New York, distanceToManhattanApprox, 15 miles]
-
A.
cityBlock
Indicates that one entity is a city block that contains, is the location of, or is otherwise spatially associated with the other entity.
-
B.
approximateDistanceFrom
chosen
Indicates an estimated or rough measure of how far one entity is from another.
-
C.
approximateGreatCircleDistanceMiles
Indicates the approximate distance, measured in miles, between two locations along the great-circle path on the surface of a sphere (typically the Earth).
-
D.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
-
E.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb9340e0819083215989718b4598 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.