Triple
T15060245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trionychidae |
E379605
|
entity |
| Predicate | plastronCharacteristic |
P48124
|
FINISHED |
| Object | reduced bony plastron |
—
|
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: reduced bony plastron | Statement: [Trionychidae, plastronCharacteristic, reduced bony plastron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plastronCharacteristic Context triple: [Trionychidae, plastronCharacteristic, reduced bony plastron]
-
A.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
-
B.
hasBodyPlanFeature
chosen
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
C.
characteristicTaxon
Indicates that one taxon is characteristic or typical of another taxonomic group, such as serving as a defining or representative member.
-
D.
carapaceLength
Indicates the measured length of an organism’s carapace from a defined anatomical reference point.
-
E.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee50afc8190bf7b0f4bbe8c60a3 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.