Triple
T26799801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burleigh Falls |
E671065
|
entity |
| Predicate | locatedBetweenLakes |
P195996
|
FINISHED |
| Object | Lovesick Lake |
—
|
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: Lovesick Lake | Statement: [Burleigh Falls, locatedBetweenLakes, Lovesick Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedBetweenLakes Context triple: [Burleigh Falls, locatedBetweenLakes, Lovesick Lake]
-
A.
locatedInLakeRegion
Indicates that the subject entity is situated within a geographic area characterized as a lake region.
-
B.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
C.
locatedBetweenGlaciers
Indicates that something is situated in the area or region separating two or more glaciers.
-
D.
connectsToByLake
Indicates that one entity is linked or joined to another specifically via a lake as the connecting medium or route.
-
E.
locatedOnGreatLake
Indicates that something is situated on the shore or directly adjacent to one of the Great Lakes.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: April 27, 2026, 4:22 a.m.