Triple
T17869044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickajack Cave |
E446781
|
entity |
| Predicate | partiallyFloodedBy |
P44338
|
FINISHED |
| Object | Nickajack 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: Nickajack Lake | Statement: [Nickajack Cave, partiallyFloodedBy, Nickajack Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyFloodedBy Context triple: [Nickajack Cave, partiallyFloodedBy, Nickajack Lake]
-
A.
partiallySubmerged
chosen
Indicates that one entity is located such that only a portion of it is below the surface of a surrounding medium (typically a liquid), while the rest remains above.
-
B.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
C.
waterFilled
Indicates that one entity is filled or occupied with water, typically to a certain level or capacity.
-
D.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
-
E.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa18df881908a8ff40b7de19268 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:18 a.m.