Triple
T2040862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rubin Ridge |
E44739
|
entity |
| Predicate | showsEvidenceOf |
P21543
|
FINISHED |
| Object | layered sedimentary bedding |
—
|
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: layered sedimentary bedding | Statement: [Rubin Ridge, showsEvidenceOf, layered sedimentary bedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsEvidenceOf Context triple: [Rubin Ridge, showsEvidenceOf, layered sedimentary bedding]
-
A.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
C.
showsThat
chosen
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
hasLanguageEvidenceOf
Indicates that there is linguistic or textual evidence supporting, documenting, or attesting to the related entity or claim.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.