Triple
T5201889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occator Crater |
E117410
|
entity |
| Predicate | saltDepositsOrigin |
P62443
|
FINISHED |
| Object | freezing of ascending brines |
—
|
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: freezing of ascending brines | Statement: [Occator Crater, saltDepositsOrigin, freezing of ascending brines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saltDepositsOrigin Context triple: [Occator Crater, saltDepositsOrigin, freezing of ascending brines]
-
A.
depositionalEnvironment
Indicates the natural setting or conditions under which sediments were originally deposited.
-
B.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
C.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
D.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
-
E.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7ad9bdd88190ae8aa6f4aba695a7 |
completed | March 20, 2026, 4:50 p.m. |
Created at: March 20, 2026, 1:47 p.m.