Triple
T1908591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camarhynchus |
E38056
|
entity |
| Predicate | beakAdaptation |
P9414
|
FINISHED |
| Object | variation in beak size and shape linked to diet |
—
|
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: variation in beak size and shape linked to diet | Statement: [Camarhynchus, beakAdaptation, variation in beak size and shape linked to diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beakAdaptation Context triple: [Camarhynchus, beakAdaptation, variation in beak size and shape linked to diet]
-
A.
beakShapeAdaptedTo
chosen
Indicates that an organism’s beak shape is specifically suited or modified to function effectively in a particular environment, diet, or ecological role.
-
B.
beakType
Indicates the specific form or structure of an entity’s beak, characterizing how it is shaped or adapted.
-
C.
hasBeak
Indicates that an entity possesses a beak as a physical anatomical feature.
-
D.
eagleBeakColor
Indicates the color attribute associated with the beak of an eagle.
-
E.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.