Triple
T720086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namib Desert |
E14396
|
entity |
| Predicate | precipitationSource |
P4102
|
FINISHED |
| Object | coastal fog is a major moisture source |
—
|
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: coastal fog is a major moisture source | Statement: [Namib Desert, precipitationSource, coastal fog is a major moisture source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precipitationSource Context triple: [Namib Desert, precipitationSource, coastal fog is a major moisture source]
-
A.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
B.
averageAnnualPrecipitation
Indicates the typical total amount of precipitation an entity receives over the course of a year, averaged across multiple years.
-
C.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
D.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
waterOrigin
Indicates the source or starting location from which the water originates or is supplied.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.