Triple
T15060243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trionychidae |
E379605
|
entity |
| Predicate | carapaceCharacteristic |
P117162
|
FINISHED |
| Object | lack of horny scutes |
—
|
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: lack of horny scutes | Statement: [Trionychidae, carapaceCharacteristic, lack of horny scutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carapaceCharacteristic Context triple: [Trionychidae, carapaceCharacteristic, lack of horny scutes]
-
A.
carapaceLength
Indicates the measured length of an organism’s carapace from a defined anatomical reference point.
-
B.
carapaceLengthRange
Indicates the minimum and maximum measured lengths of an organism’s carapace within a specified context or dataset.
-
C.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
-
D.
averageCarapaceWidth
Indicates the measured mean width of an organism’s carapace across a set of individuals or observations.
-
E.
averageCarapaceLength
Indicates the typical or mean length of an entity’s carapace, usually measured across a group or over multiple observations.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:01 a.m.