Triple
T2235759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lophiiformes |
E49274
|
entity |
| Predicate | finStructure |
P37269
|
FINISHED |
| Object | first dorsal-fin spine modified as illicium |
—
|
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: first dorsal-fin spine modified as illicium | Statement: [Lophiiformes, finStructure, first dorsal-fin spine modified as illicium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finStructure Context triple: [Lophiiformes, finStructure, first dorsal-fin spine modified as illicium]
-
A.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
B.
capitalStructure
Indicates the financial relationship defining how an entity is funded through a mix of debt, equity, and other securities.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
E.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.