Triple
T23368058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Canyon Group |
E593378
|
entity |
| Predicate | containsDeposits |
P152450
|
FINISHED |
| Object | eolian sandstone |
—
|
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: eolian sandstone | Statement: [Glen Canyon Group, containsDeposits, eolian sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDeposits Context triple: [Glen Canyon Group, containsDeposits, eolian sandstone]
-
A.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
B.
commonDeposits
Indicates that two or more entities share the same or overlapping deposit locations or accounts.
-
C.
leftDeposits
Indicates that an entity has placed or left deposits (such as money or resources) with another entity or at a particular location.
-
D.
typeOfDeposits
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
-
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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aed374819097d38f51894bee44 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:32 p.m.