Triple
T17082574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emu Bay Shale |
E414510
|
entity |
| Predicate | fossilPreservationQuality |
P77563
|
FINISHED |
| Object | exceptional |
—
|
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: exceptional | Statement: [Emu Bay Shale, fossilPreservationQuality, exceptional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilPreservationQuality Context triple: [Emu Bay Shale, fossilPreservationQuality, exceptional]
-
A.
fossilPreservation
chosen
Indicates that a fossil retains evidence of its original features or conditions through specific modes or quality of preservation.
-
B.
stateOfPreservation
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
C.
fossilTypeMaterial
Indicates that a fossil specimen serves as the designated type material (e.g., holotype, lectotype) for a named taxon.
-
D.
fossilRecordStatus
Indicates the preservation state or condition of an organism’s remains as documented in the fossil record.
-
E.
fossilRich
Indicates that a location, layer, or material contains an abundant or significant concentration of fossils.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe408d48190b4f52c2102eae7c2 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.