Triple
T37380070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansfield Hollow State Park |
E928407
|
entity |
| Predicate | hasWaterbodyName |
P187403
|
FINISHED |
| Object | Mansfield Hollow Lake |
—
|
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: Mansfield Hollow Lake | Statement: [Mansfield Hollow State Park, hasWaterbodyName, Mansfield Hollow Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterbodyName Context triple: [Mansfield Hollow State Park, hasWaterbodyName, Mansfield Hollow Lake]
-
A.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
B.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
C.
namedWaterBody
chosen
Indicates that an entity is identified as a specific water body by a given name.
-
D.
watershedName
Indicates the name assigned to the watershed with which an entity is associated.
-
E.
hydronymOf
Indicates that one term is the name of a body of water associated with another geographic entity (e.g., a river, lake, or sea named after a place or feature).
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:16 p.m.