Triple
T28817233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhaetian age |
E727670
|
entity |
| Predicate | topBoundary |
P165623
|
FINISHED |
| Object | Triassic–Jurassic boundary |
—
|
NE NERFINISHED |
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: Triassic–Jurassic boundary | Statement: [Rhaetian age, topBoundary, Triassic–Jurassic boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topBoundary Context triple: [Rhaetian age, topBoundary, Triassic–Jurassic boundary]
-
A.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
B.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
C.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
D.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
E.
topDivisionAbove
Indicates that one division or tier is hierarchically higher or superior to another within an organizational or structural ranking.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:33 a.m.