Triple
T30628187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyllige Born fountain |
E779639
|
entity |
| Predicate | waterIsBelievedTo |
P188095
|
FINISHED |
| Object | have therapeutic effects |
—
|
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: have therapeutic effects | Statement: [Hyllige Born fountain, waterIsBelievedTo, have therapeutic effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterIsBelievedTo Context triple: [Hyllige Born fountain, waterIsBelievedTo, have therapeutic effects]
-
A.
waterIsKnownFor
Indicates that something is recognized or notable for its association with water, such as its abundance, use, or characteristic relation to water.
-
B.
waterContains
Indicates that a body or volume of water holds, includes, or has within it a specified substance, object, or entity.
-
C.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
D.
waterPresence
Indicates the existence or amount of water present in or around a specified entity or location.
-
E.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 29, 2026, 8:28 p.m.