Triple
T14171705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oswego Lake |
E351222
|
entity |
| Predicate | propertyTypeAlongShore |
P113098
|
FINISHED |
| Object | single-family 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: single-family homes | Statement: [Oswego Lake, propertyTypeAlongShore, single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeAlongShore Context triple: [Oswego Lake, propertyTypeAlongShore, single-family homes]
-
A.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
B.
shorelineCharacteristic
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
C.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
D.
shorelineOwnership
Indicates that one entity holds legal or recognized ownership rights over a stretch of shoreline associated with another entity or location.
-
E.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
- F. None of above. chosen
Provenance (4 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:01 a.m.