Triple
T26373576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taxidea |
E660832
|
entity |
| Predicate | hasCharacteristicMemberTrait |
P274
|
FINISHED |
| Object | fossorial lifestyle |
—
|
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: fossorial lifestyle | Statement: [Taxidea, hasCharacteristicMemberTrait, fossorial lifestyle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicMemberTrait Context triple: [Taxidea, hasCharacteristicMemberTrait, fossorial lifestyle]
-
A.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
-
B.
subjectHasCharacteristic
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
C.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
D.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
E.
containsTrait
Indicates that one entity possesses, exhibits, or is characterized by a specified trait.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 26, 2026, 11 p.m.