Triple
T12587343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawmut Dam |
E300501
|
entity |
| Predicate | isLocatedInWaterBodyRegion |
P1714
|
FINISHED |
| Object | central Maine |
—
|
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: central Maine | Statement: [Shawmut Dam, isLocatedInWaterBodyRegion, central Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInWaterBodyRegion Context triple: [Shawmut Dam, isLocatedInWaterBodyRegion, central Maine]
-
A.
isInlandWaterBodyOf
Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
-
B.
locatedInBodyOfWater
chosen
Indicates that an entity is situated within or on the surface of a specific body of water.
-
C.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
D.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
E.
isInCountryWater
Indicates that one entity (typically a body of water or water area) is located within or belongs to the territorial waters of a specified country.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:05 p.m.