Triple
T8200148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amami rabbit |
E191547
|
entity |
| Predicate | hasUniqueGenus |
P56912
|
FINISHED |
| Object | only extant species in genus Pentalagus |
—
|
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: only extant species in genus Pentalagus | Statement: [Amami rabbit, hasUniqueGenus, only extant species in genus Pentalagus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUniqueGenus Context triple: [Amami rabbit, hasUniqueGenus, only extant species in genus Pentalagus]
-
A.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
B.
isOnlyGenusIn
chosen
Indicates that a genus is the sole genus contained within a specified higher-level taxonomic group or context.
-
C.
hasExtantGenus
Indicates that a taxonomic group currently includes at least one genus that is still living (not extinct).
-
D.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
E.
hasSolitarySpecies
Indicates that an entity includes or is associated with species that live or behave predominantly alone rather than in groups.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.