Triple
T27123261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herpestoidea |
E687055
|
entity |
| Predicate | notableMemberGenus |
P12304
|
FINISHED |
| Object | Herpestes |
—
|
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: Herpestes | Statement: [Herpestoidea, notableMemberGenus, Herpestes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberGenus Context triple: [Herpestoidea, notableMemberGenus, Herpestes]
-
A.
notableMemberTaxon
Indicates that a taxonomic group has a particular member taxon that is especially notable or representative within that group.
-
B.
notableGenus
chosen
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
-
C.
notablePetMember
Indicates that one entity is a pet that is notably associated with, or recognized as belonging to, another entity.
-
D.
notableInhabitantClass
Indicates that a place or location is known for being inhabited by a particular class or type of notable beings or entities.
-
E.
notableExtinctMember
Indicates that an extinct individual or species is a particularly significant or well-known member of a larger group or category.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: April 27, 2026, 9 a.m.