Triple
T6749247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dodo |
E154298
|
entity |
| Predicate | specimensPreservedAs |
P66838
|
FINISHED |
| Object | subfossil 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: subfossil remains | Statement: [dodo, specimensPreservedAs, subfossil remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specimensPreservedAs Context triple: [dodo, specimensPreservedAs, subfossil remains]
-
A.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
B.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
C.
isTypeSpecimen
Indicates that an entity serves as the designated type specimen upon which the formal description and name of a taxon are based.
-
D.
selectedForPreservationBy
Indicates that one entity has been chosen by another entity to be kept, maintained, or safeguarded from removal or loss.
-
E.
hasSubjectOfPreservation
chosen
Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.