Triple
T16980466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nymphaeum (Jerash) |
E411928
|
entity |
| Predicate | waterFunction |
P125469
|
FINISHED |
| Object | supplied drinking water |
—
|
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: supplied drinking water | Statement: [Nymphaeum (Jerash), waterFunction, supplied drinking water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFunction Context triple: [Nymphaeum (Jerash), waterFunction, supplied drinking water]
-
A.
waterInput
Indicates that an entity receives or is supplied with water from another source or system.
-
B.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
C.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
D.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
E.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18776c081909225620fd43aca57 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.