Triple
T4643089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chersina angulata |
E101699
|
entity |
| Predicate | hasGenusCharacteristic |
P31710
|
FINISHED |
| Object | only species in genus Chersina |
—
|
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 species in genus Chersina | Statement: [Chersina angulata, hasGenusCharacteristic, only species in genus Chersina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenusCharacteristic Context triple: [Chersina angulata, hasGenusCharacteristic, only species in genus Chersina]
-
A.
genusCharacteristic
chosen
Indicates that a particular characteristic or trait is typical of, or defining for, a given genus.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
D.
hasExtantGenus
Indicates that a taxonomic group currently includes at least one genus that is still living (not extinct).
-
E.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a93047c8190990c94fd5a57c867 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.