Triple
T4146955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namib-Naukluft National Park |
E89807
|
entity |
| Predicate | primaryMoistureSource |
P15750
|
FINISHED |
| Object | Atlantic fog |
—
|
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: Atlantic fog | Statement: [Namib-Naukluft National Park, primaryMoistureSource, Atlantic fog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMoistureSource Context triple: [Namib-Naukluft National Park, primaryMoistureSource, Atlantic fog]
-
A.
receivesMoistureFrom
chosen
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
B.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
C.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
E.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.