Triple
T26713279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreopithecus |
E673478
|
entity |
| Predicate | fossilMaterialIncludes |
P150285
|
FINISHED |
| Object | cranial remains |
—
|
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: cranial remains | Statement: [Oreopithecus, fossilMaterialIncludes, cranial remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilMaterialIncludes Context triple: [Oreopithecus, fossilMaterialIncludes, cranial remains]
-
A.
fossilTypeMaterial
Indicates that a fossil specimen serves as the designated type material (e.g., holotype, lectotype) for a named taxon.
-
B.
fossilPart
chosen
Indicates that one entity is a physical component or fragment of another entity that is a fossil.
-
C.
includesFossilSpecies
Indicates that one entity (such as a collection, site, or layer) contains or encompasses one or more fossil species as part of its contents or composition.
-
D.
containsFossilsFrom
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
E.
fossilContent
Indicates that one entity contains, preserves, or is characterized by the fossils 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:36 a.m.