Triple
T33964871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fowlerichthys |
E870822
|
entity |
| Predicate | usesLureFor |
P32782
|
FINISHED |
| Object | attracting prey |
—
|
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: attracting prey | Statement: [Fowlerichthys, usesLureFor, attracting prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLureFor Context triple: [Fowlerichthys, usesLureFor, attracting prey]
-
A.
lures
Indicates that one entity attracts, entices, or draws another entity toward itself, often by offering something appealing or deceptive.
-
B.
usesForPreyCapture
chosen
Indicates that an entity employs another entity as a means or tool for capturing prey.
-
C.
usesCaudalLuring
Indicates that an entity attracts or manipulates another by moving or displaying its tail in a way that functions as a lure.
-
D.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
E.
hasAnglingOn
Indicates that one entity is oriented or slanted at a particular angle relative to 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:50 a.m.