Triple
T344067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cretaceous–Paleogene boundary |
E6899
|
entity |
| Predicate | evidence |
P3650
|
FINISHED |
| Object | global iridium-rich clay layer |
—
|
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: global iridium-rich clay layer | Statement: [Cretaceous–Paleogene boundary, evidence, global iridium-rich clay layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidence Context triple: [Cretaceous–Paleogene boundary, evidence, global iridium-rich clay layer]
-
A.
providesEvidenceFor
chosen
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.
standardOfProof
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
-
D.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
E.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0019088190a9b969c4287dc4fa |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.