Triple
T1798782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genlisea |
E39665
|
entity |
| Predicate | hasTrapType |
P32024
|
FINISHED |
| Object | underground leaf traps |
—
|
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: underground leaf traps | Statement: [Genlisea, hasTrapType, underground leaf traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrapType Context triple: [Genlisea, hasTrapType, underground leaf traps]
-
A.
hasTriggerType
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
-
B.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
C.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.