Triple
T19973858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molopo River basin |
E493635
|
entity |
| Predicate | surfaceFlowFrequency |
P138102
|
FINISHED |
| Object | infrequent |
—
|
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: infrequent | Statement: [Molopo River basin, surfaceFlowFrequency, infrequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceFlowFrequency Context triple: [Molopo River basin, surfaceFlowFrequency, infrequent]
-
A.
surfaceCurrent
Indicates that one entity is the prevailing flow or movement of a fluid (such as water or air) along the surface of another entity.
-
B.
flowRelativeToSurface
Indicates that a flow moves in relation to a specified surface, capturing its direction, alignment, or behavior with respect to that surface.
-
C.
surfacePressure
Indicates the pressure exerted by a fluid (such as air or water) on the surface of an object or body.
-
D.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
E.
seasonalFlow
Indicates that the flow or intensity of something varies in a recurring pattern according to the seasons.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65bcb72048190aedb4f085ace0493 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:17 p.m.