Triple
T37535863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xenorhabdus |
E933192
|
entity |
| Predicate | secretionSystem |
P188705
|
FINISHED |
| Object | type III secretion system |
—
|
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: type III secretion system | Statement: [Xenorhabdus, secretionSystem, type III secretion system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretionSystem Context triple: [Xenorhabdus, secretionSystem, type III secretion system]
-
A.
secreted
Indicates that one entity releases or emits another substance or material, typically as part of a biological or chemical process.
-
B.
secretedInResponseTo
Indicates that a substance is released or discharged as a direct reaction to a specific stimulus, condition, or event.
-
C.
excretorySystem
Indicates the relationship in which an entity functions as, or is part of, the biological system responsible for removing waste products from an organism.
-
D.
leafSecretionType
Indicates the type or nature of substances secreted by a plant’s leaves.
-
E.
isExcretedVia
Indicates that a substance or waste product leaves an organism’s body through a specified anatomical route or excretory mechanism.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.