Triple
T36284277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastes wilsoni |
E893028
|
entity |
| Predicate | analFinSoftRays |
P53792
|
FINISHED |
| Object | 6 to 8 |
—
|
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: 6 to 8 | Statement: [Sebastes wilsoni, analFinSoftRays, 6 to 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analFinSoftRays Context triple: [Sebastes wilsoni, analFinSoftRays, 6 to 8]
-
A.
financialHubFor
Indicates a relationship where one entity serves as a central location or primary center for managing, coordinating, or facilitating the financial activities of another entity or group.
-
B.
mainFinancier
Indicates that one entity serves as the primary provider of financial support or funding for another entity or activity.
-
C.
alsoProvidesFinanceIn
Indicates that an entity, in addition to other roles or services, supplies financial support or funding within a specified context or location.
-
D.
analFins
chosen
Indicates that one entity possesses or is characterized by anal fins in relation to another specified context or classification.
-
E.
financialCharacteristic
Indicates that one entity has a particular financial attribute, status, or property in relation to another entity or context.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.