Triple
T2940038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salton Trough |
E79362
|
entity |
| Predicate | filledBy |
P13702
|
FINISHED |
| Object | sedimentary deposits |
—
|
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: sedimentary deposits | Statement: [Salton Trough, filledBy, sedimentary deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filledBy Context triple: [Salton Trough, filledBy, sedimentary deposits]
-
A.
isTypicallyFilledWith
chosen
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
B.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
C.
repopulatedBy
Indicates that something is populated again or refilled with members or inhabitants by a specified agent or source.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986d9a248190927efc1a0c7d247f |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.