Triple
T2661281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepenthes rajah |
E54730
|
entity |
| Predicate | feedingStrategy |
P10557
|
FINISHED |
| Object | pitfall trap |
—
|
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: pitfall trap | Statement: [Nepenthes rajah, feedingStrategy, pitfall trap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedingStrategy Context triple: [Nepenthes rajah, feedingStrategy, pitfall trap]
-
A.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
B.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
C.
foragingStrategy
chosen
Indicates the method or pattern an organism uses to search for, obtain, and exploit food resources.
-
D.
feedConversionEfficiency
Indicates how efficiently input feed is converted into desired output (such as growth, product, or energy) in a biological or production system.
-
E.
includesFeedingType
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.