Triple
T33836152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antennarius |
E867238
|
entity |
| Predicate | illiciumFunction |
P177760
|
FINISHED |
| Object | acts as a fishing rod-like lure |
—
|
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: acts as a fishing rod-like lure | Statement: [Antennarius, illiciumFunction, acts as a fishing rod-like lure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illiciumFunction Context triple: [Antennarius, illiciumFunction, acts as a fishing rod-like lure]
-
A.
clitellumFunction
Indicates the functional role or purpose of an organism’s clitellum in a biological or reproductive context.
-
B.
cuticleFunction
Indicates the functional role or purpose that a cuticle serves in relation to an organism or structure.
-
C.
forcipulesFunction
Indicates the functional role or use of an organism’s forcipules (modified front legs used as grasping or venom-delivery appendages).
-
D.
cucullusFunction
Indicates that one entity serves as the functional hood- or cowl-like covering (cucullus) for another entity.
-
E.
fingerFunction
Indicates that a finger performs or is associated with a particular function or role in an action or system.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.