Triple
T16171371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSSP at Aidaralash Creek, Kazakhstan (base of Asselian) |
E392443
|
entity |
| Predicate | liesAbove |
P12702
|
FINISHED |
| Object | uppermost Carboniferous strata |
—
|
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: uppermost Carboniferous strata | Statement: [GSSP at Aidaralash Creek, Kazakhstan (base of Asselian), liesAbove, uppermost Carboniferous strata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesAbove Context triple: [GSSP at Aidaralash Creek, Kazakhstan (base of Asselian), liesAbove, uppermost Carboniferous strata]
-
A.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
B.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
C.
liesIn
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
D.
liesToThe
Indicates that one entity intentionally provides false or misleading information to another entity.
-
E.
existsBelow
chosen
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.