Triple
T36999152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | three-spined stickleback |
E915304
|
entity |
| Predicate | hasPelvicSpines |
P38803
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [three-spined stickleback, hasPelvicSpines, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPelvicSpines Context triple: [three-spined stickleback, hasPelvicSpines, present]
-
A.
hasSpines
chosen
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
B.
hasPelvicFins
Indicates that the subject possesses pelvic fins as anatomical structures.
-
C.
pelvisMorphology
Indicates the structural characteristics or shape-related features of a pelvis in relation to another entity or condition.
-
D.
pelvicGirdleAttachment
Indicates the anatomical relationship by which a pelvic girdle is connected or attached to another skeletal structure or body region.
-
E.
dorsalSpineCharacteristic
Indicates a relationship specifying the particular features or qualities of an entity’s dorsal spine (such as shape, size, structure, or other defining attributes).
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:14 p.m.