Triple
T29093352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sinks |
E734920
|
entity |
| Predicate | surfaceWaterBehavior |
P166917
|
FINISHED |
| Object | stream vanishes underground |
—
|
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: stream vanishes underground | Statement: [The Sinks, surfaceWaterBehavior, stream vanishes underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterBehavior Context triple: [The Sinks, surfaceWaterBehavior, stream vanishes underground]
-
A.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
B.
surfaceWaterOutlet
Indicates a relationship where surface water from one location flows out or is discharged through a specific outlet or exit point.
-
C.
usesSurfaceWater
Indicates that one entity relies on or draws from surface water sources (such as rivers, lakes, or reservoirs) for its activities or needs.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
affectsWaterBody
Indicates that one entity has an impact on the condition, quality, or state of a water body.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 11:06 a.m.