Triple
T32981589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkley, Massachusetts |
E843813
|
entity |
| Predicate | distanceToBostonKm |
P798
|
FINISHED |
| Object | about 64 |
—
|
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 64 | Statement: [Berkley, Massachusetts, distanceToBostonKm, about 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBostonKm Context triple: [Berkley, Massachusetts, distanceToBostonKm, about 64]
-
A.
distanceFromBoston
chosen
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceToBostonByRoad
Indicates the road travel distance between a given location and Boston.
-
C.
distanceToNewYorkCity
Indicates the spatial distance between a given entity’s location and New York City.
-
D.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
-
E.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:22 a.m.