Triple
T7022994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Ann’s Well |
E162872
|
entity |
| Predicate | waterEmergesFrom |
P4102
|
FINISHED |
| Object | deep underground aquifer |
—
|
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: deep underground aquifer | Statement: [St Ann’s Well, waterEmergesFrom, deep underground aquifer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterEmergesFrom Context triple: [St Ann’s Well, waterEmergesFrom, deep underground aquifer]
-
A.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterFilled
Indicates that one entity is filled or occupied with water, typically to a certain level or capacity.
-
C.
waterFeature
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
D.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
E.
waterPresence
Indicates the existence or amount of water present in or around a specified entity or location.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.