Triple
T27382087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwin Lake |
E691256
|
entity |
| Predicate | hasShoreDevelopment |
P25009
|
FINISHED |
| Object | private homes |
—
|
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: private homes | Statement: [Baldwin Lake, hasShoreDevelopment, private homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoreDevelopment Context triple: [Baldwin Lake, hasShoreDevelopment, private homes]
-
A.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
B.
hasWaterfrontDevelopment
chosen
Indicates that a location or property includes or is associated with constructed developments directly along or adjacent to a body of water.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 12:23 p.m.