Triple
T29398210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester–Boston Regional Airport |
E745559
|
entity |
| Predicate | distanceFromBoston_milesApprox |
P798
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Manchester–Boston Regional Airport, distanceFromBoston_milesApprox, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBoston_milesApprox Context triple: [Manchester–Boston Regional Airport, distanceFromBoston_milesApprox, 50]
-
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.
distanceFromProvincetownCenterMiles
Indicates the number of miles between an entity’s location and the center of Provincetown.
-
D.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
-
E.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: April 28, 2026, 2:48 p.m.