Triple
T28817575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhaetian Stage |
E727681
|
entity |
| Predicate | upperBoundaryDefines |
P129448
|
FINISHED |
| Object | base of Hettangian Stage |
—
|
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: base of Hettangian Stage | Statement: [Rhaetian Stage, upperBoundaryDefines, base of Hettangian Stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperBoundaryDefines Context triple: [Rhaetian Stage, upperBoundaryDefines, base of Hettangian Stage]
-
A.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
B.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
C.
topBoundary
Indicates that one entity serves as the uppermost limit, edge, or border of another entity or region.
-
D.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
E.
boundedSuperiorlyBy
chosen
Indicates that one entity serves as the upper or top boundary limit of 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:33 a.m.