Triple
T18410591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballville Dam site |
E441746
|
entity |
| Predicate | postRemovalUse |
P104636
|
FINISHED |
| Object | riverine habitat |
—
|
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: riverine habitat | Statement: [Ballville Dam site, postRemovalUse, riverine habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRemovalUse Context triple: [Ballville Dam site, postRemovalUse, riverine habitat]
-
A.
postExpulsionUse
Indicates the use or treatment of something after it has been expelled, removed, or discharged from its original context or container.
-
B.
afterRemoval
chosen
Indicates that a condition, state, or relationship holds only once a specified entity or element has been removed.
-
C.
removal
Indicates the action or process by which something is taken away, eliminated, or detached from something else.
-
D.
useAfterRenovation
Indicates that something is intended to be used or occupied only after renovation work has been completed.
-
E.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5195df3288190be61f4053476c735 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.