Triple
T33720807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madagascar rainbowfishes |
E864005
|
entity |
| Predicate | finShape |
P109283
|
FINISHED |
| Object | elongated dorsal and anal fins in many species |
—
|
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: elongated dorsal and anal fins in many species | Statement: [Madagascar rainbowfishes, finShape, elongated dorsal and anal fins in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finShape Context triple: [Madagascar rainbowfishes, finShape, elongated dorsal and anal fins in many species]
-
A.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
B.
shapeType
chosen
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
E.
الشكل
Indicates a relationship where one entity represents, takes, or describes the form, shape, or configuration of another entity.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6faeac9288190ac7ce78ea3cdb622 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.