Triple
T28495915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleocene |
E721105
|
entity |
| Predicate | lowerBoundaryCoincidesWith |
P39203
|
FINISHED |
| Object | iridium-rich clay layer at K–Pg boundary |
—
|
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: iridium-rich clay layer at K–Pg boundary | Statement: [Paleocene, lowerBoundaryCoincidesWith, iridium-rich clay layer at K–Pg boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundaryCoincidesWith Context triple: [Paleocene, lowerBoundaryCoincidesWith, iridium-rich clay layer at K–Pg boundary]
-
A.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
-
B.
hasLowerBoundaryDefinedBy
chosen
Indicates that one entity’s lower limit, edge, or boundary is specified or determined by another entity.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
E.
endBoundaryDefinedBy
Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by another entity.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 3:04 a.m.