Triple
T41612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayer |
E820
|
entity |
| Predicate | distanceToBostonByRoad_km |
P798
|
FINISHED |
| Object | approximately 56 |
—
|
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 56 | Statement: [Ayer, distanceToBostonByRoad_km, approximately 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBostonByRoad_km Context triple: [Ayer, distanceToBostonByRoad_km, approximately 56]
-
A.
distanceFromBoston
chosen
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
C.
distanceToNewYorkCity
Indicates the spatial distance between a given entity’s location and New York City.
-
D.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24db9527c8190816b6b25c88cb2f4 |
completed | Feb. 28, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69a24ab8a8908190beec6da6694dd4c9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.