Triple
T10105850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarcopterygii |
E216317
|
entity |
| Predicate | differenceFromActinopterygii |
P92450
|
FINISHED |
| Object | fins with robust internal skeleton |
—
|
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: fins with robust internal skeleton | Statement: [Sarcopterygii, differenceFromActinopterygii, fins with robust internal skeleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromActinopterygii Context triple: [Sarcopterygii, differenceFromActinopterygii, fins with robust internal skeleton]
-
A.
isJawless
Indicates that an entity lacks a jaw or does not possess a true jaw structure.
-
B.
dorsalFinType
Indicates the specific kind or morphology of dorsal fin that an entity possesses.
-
C.
dorsalFinPosition
Indicates the relative location of an entity’s dorsal fin along its body.
-
D.
hasDorsalFin
Indicates that an entity possesses a dorsal fin as a physical anatomical feature.
-
E.
swimBladder
Indicates that an entity possesses or is associated with a swim bladder, an internal gas-filled organ used to control buoyancy in water.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09dde888190bb550a3cd0b204fe |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:03 p.m.