Triple
T35444086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Harriet refectory |
E1024433
|
entity |
| Predicate | waterBodyServed |
P5565
|
FINISHED |
| Object | Lake Harriet |
—
|
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: Lake Harriet | Statement: [Lake Harriet refectory, waterBodyServed, Lake Harriet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyServed Context triple: [Lake Harriet refectory, waterBodyServed, Lake Harriet]
-
A.
watercourseTypeServed
Indicates the type of watercourse (e.g., river, canal, stream) that is supplied, supported, or otherwise served by a given feature or system.
-
B.
waterwayServed
chosen
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
D.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
E.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:04 p.m.