Triple
T8322125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Spring |
E194857
|
entity |
| Predicate | hasFlowRate |
P5503
|
FINISHED |
| Object | over 1 million litres per day |
—
|
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: over 1 million litres per day | Statement: [Sacred Spring, hasFlowRate, over 1 million litres per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlowRate Context triple: [Sacred Spring, hasFlowRate, over 1 million litres per day]
-
A.
waterFlowRate
chosen
Indicates the rate at which water moves or is transported through a given point or system over time.
-
B.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
C.
hasCoolingFlow
Indicates that an entity is equipped with or utilizes a system or mechanism to remove heat or maintain a lower temperature through the flow of a cooling medium.
-
D.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
E.
glacierFlowRate
Indicates the rate at which a glacier moves or flows over a given distance in a specified time.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f693ad08190ad4ce6269a61eb3f |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.