Triple
T30601029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Weymouth |
E778904
|
entity |
| Predicate | isPartOfCoastalTown |
P104129
|
FINISHED |
| Object | Weymouth, Massachusetts |
—
|
NE NERFINISHED |
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: Weymouth, Massachusetts | Statement: [East Weymouth, isPartOfCoastalTown, Weymouth, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCoastalTown Context triple: [East Weymouth, isPartOfCoastalTown, Weymouth, Massachusetts]
-
A.
isInCoastalTown
chosen
Indicates that one entity (typically a place or object) is located within a town that is situated along a coast.
-
B.
includesCoastalTown
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
C.
isCoastalLocality
Indicates that a locality is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
-
D.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
-
E.
isCoastalResidentialAreaOf
Indicates that a residential area is located along or near the coast of a specified geographic or administrative region.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 29, 2026, 8:25 p.m.