Triple
T14228569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Tuxedo |
E352689
|
entity |
| Predicate | hasSpeciesCharacteristic |
P99469
|
FINISHED |
| Object | anthropomorphic |
—
|
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: anthropomorphic | Statement: [Tennessee Tuxedo, hasSpeciesCharacteristic, anthropomorphic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciesCharacteristic Context triple: [Tennessee Tuxedo, hasSpeciesCharacteristic, anthropomorphic]
-
A.
characteristicTaxon
Indicates that one taxon is characteristic or typical of another taxonomic group, such as serving as a defining or representative member.
-
B.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
C.
subjectHasCharacteristic
chosen
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
genusCharacteristic
Indicates that a particular characteristic or trait is typical of, or defining for, a given genus.
-
E.
hasSpeciesRole
Indicates that an entity plays a specific functional or categorical role within a particular species.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622a48508190bbfedb762bd1674d |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.