Triple
T27326844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 495 in Massachusetts |
E689674
|
entity |
| Predicate | westernArcLocation |
P4239
|
FINISHED |
| Object | inland from 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: inland from Boston | Statement: [Interstate 495 in Massachusetts, westernArcLocation, inland from Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernArcLocation Context triple: [Interstate 495 in Massachusetts, westernArcLocation, inland from Boston]
-
A.
locatedWestOf
chosen
Indicates that one entity is positioned geographically to the west of another entity.
-
B.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
C.
eraLocation
Indicates the place or geographic context in which a particular historical era or time period occurs or is primarily associated.
-
D.
isWesternmostPartOf
Indicates that one entity is the furthest to the west within the geographic extent or boundary of another entity.
-
E.
EasternView
Indicates a spatial relationship where one entity is oriented toward, faces, or has a view in the eastern direction relative to another reference point or 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627eea1d08190aa3733b460c43b6e |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:36 a.m.