Triple
T35307281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trichoptera |
E1019669
|
entity |
| Predicate | silkProducedBy |
P137159
|
FINISHED |
| Object | labial glands |
—
|
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: labial glands | Statement: [Trichoptera, silkProducedBy, labial glands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: silkProducedBy Context triple: [Trichoptera, silkProducedBy, labial glands]
-
A.
hasSilkGlands
chosen
Indicates that an entity possesses specialized glands capable of producing silk.
-
B.
carpetWeavingRecognizedBy
Indicates that the act or tradition of carpet weaving is formally acknowledged, honored, or certified by a particular person, group, or institution.
-
C.
hasSilksDescription
Indicates that an entity has an associated textual description of its silks (e.g., colors or patterns of racing attire or similar fabric-based identifiers).
-
D.
usesLarvalSilkFor
Indicates that an organism employs silk produced during its larval stage for a specified purpose or function.
-
E.
isMajorProducerOf
Indicates that an entity plays a leading or highly significant role in producing or supplying a particular product, resource, or output.
- 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.