Triple
T27276636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griphopithecus |
E688210
|
entity |
| Predicate | fossilsDescribedFrom |
P123156
|
FINISHED |
| Object | Miocene deposits |
—
|
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: Miocene deposits | Statement: [Griphopithecus, fossilsDescribedFrom, Miocene deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilsDescribedFrom Context triple: [Griphopithecus, fossilsDescribedFrom, Miocene deposits]
-
A.
describedAsFossil
Indicates that something is characterized or identified as a fossil.
-
B.
fossilDiscoverer
Indicates the relationship in which an agent is the one who discovered or unearthed a particular fossil.
-
C.
containsFossilsFrom
chosen
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
D.
fossilRecordType
Indicates the classification of how a fossil is preserved or represented in the geological record (e.g., body fossil, trace fossil, cast, mold).
-
E.
geologicalPeriodFossils
Indicates that a particular geological period is characterized or evidenced by the presence of specific 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:03 a.m.