Triple
T32713385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eretmochelys imbricata |
E836456
|
entity |
| Predicate | hasBeakShape |
P12299
|
FINISHED |
| Object | narrow pointed beak |
—
|
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: narrow pointed beak | Statement: [Eretmochelys imbricata, hasBeakShape, narrow pointed beak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeakShape Context triple: [Eretmochelys imbricata, hasBeakShape, narrow pointed beak]
-
A.
hasBeak
Indicates that an entity possesses a beak as a physical anatomical feature.
-
B.
beakType
chosen
Indicates the specific form or structure of an entity’s beak, characterizing how it is shaped or adapted.
-
C.
hasBeakFunction
Indicates that an entity’s beak performs or is associated with a particular function or role.
-
D.
hasBeakColor
Indicates that an entity possesses a beak characterized by a specific color.
-
E.
beakShapeAdaptedTo
Indicates that an organism’s beak shape is specifically suited or modified to function effectively in a particular environment, diet, or ecological role.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:11 a.m.