Triple
T35307319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trichoptera |
E1019669
|
entity |
| Predicate | caseFunction |
P178290
|
FINISHED |
| Object | protection from predators |
—
|
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: protection from predators | Statement: [Trichoptera, caseFunction, protection from predators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseFunction Context triple: [Trichoptera, caseFunction, protection from predators]
-
A.
scriptCodeCase
Indicates how the script code is represented with respect to letter casing (e.g., uppercase, lowercase, or mixed case).
-
B.
usesCase
chosen
Indicates that one entity employs, applies, or makes practical use of another entity for a particular purpose or function.
-
C.
coversFunction
Indicates that one entity provides sufficient scope or capability to perform, include, or account for the function of another entity.
-
D.
caseReached
Indicates that a particular case, situation, or legal matter has arrived at, been brought before, or come under the consideration of a specified authority, stage, or entity.
-
E.
caseAssignmentMethod
Indicates the method or procedure by which a case is assigned to a responsible party or system.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790522fbc81908a918eda08edd6e1 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.