Triple
T1102412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salar de Uyuni |
E25408
|
entity |
| Predicate | formationType |
P23125
|
FINISHED |
| Object | evaporite deposit |
—
|
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: evaporite deposit | Statement: [Salar de Uyuni, formationType, evaporite deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationType Context triple: [Salar de Uyuni, formationType, evaporite deposit]
-
A.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
B.
formationPrinciple
Indicates the underlying rule, pattern, or principle according to which something is formed, structured, or brought into existence.
-
C.
representationType
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
-
D.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
formationMechanism
Indicates the process or mechanism by which something is formed, created, or brought into existence.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c21c2c8190a34d91a7afed23a9 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:43 p.m.