Triple
T34667739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luvaridae |
E890298
|
entity |
| Predicate | skeletonClass |
P172742
|
FINISHED |
| Object | ray-finned fishes |
—
|
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: ray-finned fishes | Statement: [Luvaridae, skeletonClass, ray-finned fishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skeletonClass Context triple: [Luvaridae, skeletonClass, ray-finned fishes]
-
A.
skeleton
Indicates that one entity serves as the basic structural framework or underlying support for another.
-
B.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
-
C.
hasSkeleton
Indicates that an entity possesses a skeleton as part of its bodily structure.
-
D.
skeletonTypeDetail
chosen
Indicates the specific structural or categorical subtype within a broader skeleton or framework classification.
-
E.
skeletonLacks
Indicates that an entity’s skeleton does not possess or is missing a specified bone, feature, or structural component.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f904b0819091ffa4ea4621e8b4 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.