Triple
T32938389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonesome George |
E842593
|
entity |
| Predicate | bodyPreservedAs |
P89806
|
FINISHED |
| Object | taxidermy specimen |
—
|
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: taxidermy specimen | Statement: [Lonesome George, bodyPreservedAs, taxidermy specimen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPreservedAs Context triple: [Lonesome George, bodyPreservedAs, taxidermy specimen]
-
A.
preservedPart
Indicates that one entity is a remaining or conserved portion of another entity that has been kept intact over time.
-
B.
preservedFor
Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
-
C.
somePreservedAs
chosen
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, or condition.
-
D.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
E.
preservedFrom
Indicates that something has been protected or kept safe from a particular source of damage, loss, or alteration.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d10d78d08190a7e0f6ed3b827322 |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.