Triple
T29968503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepacton, New York |
E761254
|
entity |
| Predicate | nowUnder |
P20246
|
FINISHED |
| Object | water level of Pepacton Reservoir |
—
|
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: water level of Pepacton Reservoir | Statement: [Pepacton, New York, nowUnder, water level of Pepacton Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nowUnder Context triple: [Pepacton, New York, nowUnder, water level of Pepacton Reservoir]
-
A.
now
Indicates that an action, state, or relationship is occurring at the present moment in time.
-
B.
under
chosen
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
C.
nowConsidered
Indicates that something has come to be regarded or classified in a particular way at the present time, possibly differing from how it was regarded before.
-
D.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
E.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786c984c8190b7668a6232901b30 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:31 p.m.