Triple
T34614497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac aux Pingualuit Plateau |
E888825
|
entity |
| Predicate | surfaceWaterFeature |
P45851
|
FINISHED |
| Object | crater lake |
—
|
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: crater lake | Statement: [Lac aux Pingualuit Plateau, surfaceWaterFeature, crater lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterFeature Context triple: [Lac aux Pingualuit Plateau, surfaceWaterFeature, crater lake]
-
A.
surfaceWater
chosen
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
B.
surfaceWaterBehavior
Indicates how surface water behaves or changes under certain conditions or over time.
-
C.
surfaceWaterOutlet
Indicates a relationship where surface water from one location flows out or is discharged through a specific outlet or exit point.
-
D.
hydrologyFeature
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
-
E.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.