Triple
T949434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worcester, Massachusetts |
E20486
|
entity |
| Predicate | distanceToBoston |
P798
|
FINISHED |
| Object | approximately 40 miles west of Boston |
—
|
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 40 miles west of Boston | Statement: [Worcester, Massachusetts, distanceToBoston, approximately 40 miles west of Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBoston Context triple: [Worcester, Massachusetts, distanceToBoston, approximately 40 miles west of Boston]
-
A.
distanceFromBoston
chosen
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceToNewYorkCity
Indicates the spatial distance between a given entity’s location and New York City.
-
C.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
-
D.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
E.
distanceToWashingtonDC
Indicates the physical distance between a given location and Washington, D.C.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3c191ac819099ebf3cb32f096d8 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.