Triple
T26158833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbiliomycetes |
E660046
|
entity |
| Predicate | nematodeTrappingMechanism |
P31463
|
FINISHED |
| Object | adhesive networks in some species |
—
|
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: adhesive networks in some species | Statement: [Orbiliomycetes, nematodeTrappingMechanism, adhesive networks in some species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nematodeTrappingMechanism Context triple: [Orbiliomycetes, nematodeTrappingMechanism, adhesive networks in some species]
-
A.
preyCaptureMechanism
chosen
Indicates the method or strategy an organism uses to locate, seize, and secure its prey.
-
B.
isEntomopathogenic
Indicates that an organism causes disease or death specifically in insects.
-
C.
nutrientUptake
Indicates the process by which an entity absorbs or takes in nutrients from its surrounding environment.
-
D.
usesLarvalSilkFor
Indicates that an organism employs silk produced during its larval stage for a specified purpose or function.
-
E.
usesForPreyCapture
Indicates that an entity employs another entity as a means or tool for capturing prey.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c12d3708190ac08d8b7c8ff48a5 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:29 p.m.