Triple
T32238378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Front Park at Lake St. Clair |
E823532
|
entity |
| Predicate | accessesWaterbody |
P98448
|
FINISHED |
| Object | Lake St. Clair |
—
|
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 St. Clair | Statement: [Lake Front Park at Lake St. Clair, accessesWaterbody, Lake St. Clair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesWaterbody Context triple: [Lake Front Park at Lake St. Clair, accessesWaterbody, Lake St. Clair]
-
A.
touchesBodyOfWater
chosen
Indicates that one entity is in direct physical contact with the surface or boundary of a body of water.
-
B.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
C.
affectsWaterBody
Indicates that one entity has an impact on the condition, quality, or state of a water body.
-
D.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
E.
involvesBodyOfWater
Indicates that the relationship or event includes, affects, or takes place in connection with a body of water such as a sea, lake, river, or ocean.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 12:39 a.m.