Triple
T31265968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirovia Ocean |
E797252
|
entity |
| Predicate | hasNoDirectFossilRecord |
P202491
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mirovia Ocean, hasNoDirectFossilRecord, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDirectFossilRecord Context triple: [Mirovia Ocean, hasNoDirectFossilRecord, true]
-
A.
hasFossilEvidence
Indicates that there exists fossil-based evidence supporting the existence, occurrence, or characteristics of the related entity or event.
-
B.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
C.
fossilRecordStatus
Indicates the preservation state or condition of an organism’s remains as documented in the fossil record.
-
D.
fossilRecordExtendsBackTo
Indicates that the existence or presence of something is documented in the fossil record as originating from a specified time or geological period.
-
E.
knownFromFossils
Indicates that the existence or occurrence of something is inferred or established based on fossil evidence.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
| PDg | Predicate description generation | batch_6a008ac2d0dc8190865ccedb2003d0ed |
completed | May 10, 2026, 1:40 p.m. |
Created at: April 29, 2026, 9:12 p.m.