Triple
T38432177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawley, Massachusetts |
E903832
|
entity |
| Predicate | notableNearbyRoute |
P49834
|
FINISHED |
| Object | Massachusetts Route 2 (Mohawk Trail) |
E17442
|
NE 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: Massachusetts Route 2 (Mohawk Trail) | Statement: [Hawley, Massachusetts, notableNearbyRoute, Massachusetts Route 2 (Mohawk Trail)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNearbyRoute Context triple: [Hawley, Massachusetts, notableNearbyRoute, Massachusetts Route 2 (Mohawk Trail)]
-
A.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
B.
nearbyMajorRoad
chosen
Indicates that one entity is located close to a significant or heavily used road.
-
C.
nearHistoricalRoute
Indicates that one entity is located close to a historically significant route or pathway.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
- F. None of above.
Provenance (4 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c29299d88190b51a3d08bbe8a754 |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.