Triple
T34001118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuiterichthys |
E871820
|
entity |
| Predicate | usesForFeeding |
P179732
|
FINISHED |
| Object | lure-like appendage to attract 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: lure-like appendage to attract prey | Statement: [Kuiterichthys, usesForFeeding, lure-like appendage to attract prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForFeeding Context triple: [Kuiterichthys, usesForFeeding, lure-like appendage to attract prey]
-
A.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
B.
usesFood
Indicates that one entity employs or consumes a food item as a resource, ingredient, or means to achieve some purpose.
-
C.
doesNotFeedOn
Indicates that one entity does not use another entity as a source of food or nourishment.
-
D.
notableFeedingBehavior
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
-
E.
isMajorFoodSourceFor
Indicates that something serves as a primary or significant source of food for another entity.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:50 a.m.