Triple
T7197054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newburyport/Rockport Line |
E168640
|
entity |
| Predicate | servesCommunity |
P82
|
FINISHED |
| Object | Rockport |
E34316
|
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: Rockport | Statement: [Newburyport/Rockport Line, servesCommunity, Rockport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rockport Context triple: [Newburyport/Rockport Line, servesCommunity, Rockport]
-
A.
Rockport
chosen
Rockport is a small coastal town on Cape Ann in northeastern Massachusetts, known for its picturesque harbor, rocky shoreline, and thriving arts community.
-
B.
Montrose
Montrose is a small town located in Dane County in the state of Wisconsin, United States.
-
C.
Montrose
Montrose is a residential neighborhood within the town of Wakefield in Middlesex County, Massachusetts.
-
D.
Montrose
Montrose is a coastal town in eastern Scotland known for its historic harbor, sandy beach, and surrounding nature reserves.
-
E.
Montrose
Montrose is a vibrant, artsy neighborhood in Houston, Texas, known for its eclectic culture, historic homes, and diverse community.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e928ecdc8190a7f3feaf6d28781b |
completed | March 27, 2026, 8:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cbe7d42c8190915fd0713523cbb0 |
completed | March 28, 2026, 12:39 p.m. |
Created at: March 27, 2026, 2:51 p.m.