Triple
T11522828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Lake |
E273208
|
entity |
| Predicate | shorelineCharacter |
P71569
|
FINISHED |
| Object | largely residential |
—
|
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: largely residential | Statement: [Black Lake, shorelineCharacter, largely residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineCharacter Context triple: [Black Lake, shorelineCharacter, largely residential]
-
A.
shorelineCharacteristic
chosen
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
B.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
C.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
D.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
E.
shore
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.