Triple
T36663466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messinian Salinity Crisis |
E905194
|
entity |
| Predicate | mainDeposits |
P186132
|
FINISHED |
| Object | evaporites |
—
|
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: evaporites | Statement: [Messinian Salinity Crisis, mainDeposits, evaporites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeposits Context triple: [Messinian Salinity Crisis, mainDeposits, evaporites]
-
A.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
B.
leftDeposits
Indicates that an entity has placed or left deposits (such as money or resources) with another entity or at a particular location.
-
C.
commonDeposits
Indicates that two or more entities share the same or overlapping deposit locations or accounts.
-
D.
containsDeposits
Indicates that one entity holds, includes, or has within it one or more deposits associated with another entity.
-
E.
typicalDeposits
Indicates that the associated value represents the usual or standard amount of deposits expected for an entity or account.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.