Triple
T31552616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobitis |
E805044
|
entity |
| Predicate | hasSuborbitalSpine |
P38803
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cobitis, hasSuborbitalSpine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuborbitalSpine Context triple: [Cobitis, hasSuborbitalSpine, yes]
-
A.
hasSpines
chosen
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
B.
hasGraspingSpinesOn
Indicates that one entity possesses grasping spines located on a specified part or surface of another entity.
-
C.
hasGraspingSpines
Indicates that an entity possesses specialized spine-like structures used for grasping or holding objects or other entities.
-
D.
hasEndoskeleton
Indicates that an entity possesses an internal supporting skeleton structure within its body.
-
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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 30, 2026, 10:11 p.m.