Triple
T34707081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roridulaceae |
E1000534
|
entity |
| Predicate | trapMovement |
P181716
|
FINISHED |
| Object | non-motile 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: non-motile traps | Statement: [Roridulaceae, trapMovement, non-motile traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trapMovement Context triple: [Roridulaceae, trapMovement, non-motile traps]
-
A.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
B.
coveredMovement
Indicates that one entity moves while being physically shielded, concealed, or protected by another entity or environmental feature.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
E.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.