Triple
T21383215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singletary Lake |
E527416
|
entity |
| Predicate | hasWaterBodyCategory |
P92225
|
FINISHED |
| Object | inland 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: inland lake | Statement: [Singletary Lake, hasWaterBodyCategory, inland lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterBodyCategory Context triple: [Singletary Lake, hasWaterBodyCategory, inland lake]
-
A.
hasBodyOfWaterType
chosen
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
B.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
C.
hasAreaWaterBody
Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
-
D.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
E.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0f05278819096c511035ffc9777 |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:12 p.m.