Triple
T33310120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsavo man-eaters |
E852849
|
entity |
| Predicate | remainsForm |
P176472
|
FINISHED |
| Object | taxidermy mounts |
—
|
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 mounts | Statement: [Tsavo man-eaters, remainsForm, taxidermy mounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsForm Context triple: [Tsavo man-eaters, remainsForm, taxidermy mounts]
-
A.
backForm
Indicates that an entity serves as a reverse, supporting, or rear-facing structure or configuration relative to another entity or form.
-
B.
laterForms
Indicates that one entity is a subsequent or more recent form, version, or stage of another entity in a temporal or developmental sequence.
-
C.
reclamationForm
Indicates that an entity is associated with a specific form or document used to request or process reclamation (e.g., recovery, return, or restoration of something).
-
D.
extantForm
Indicates that a given entity currently exists in a particular form or manifestation.
-
E.
daemonForms
Indicates that one entity takes the form of, manifests as, or is represented by a daemon associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:33 a.m.