Triple
T37449867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shigella |
E930645
|
entity |
| Predicate | invasionMechanism |
P113615
|
FINISHED |
| Object | cell invasion and intracellular spread |
—
|
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: cell invasion and intracellular spread | Statement: [Shigella, invasionMechanism, cell invasion and intracellular spread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasionMechanism Context triple: [Shigella, invasionMechanism, cell invasion and intracellular spread]
-
A.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
B.
invadesFrom
Indicates that one entity initiates an invasion or aggressive incursion into another entity starting from a specified origin or source location.
-
C.
infectionMethod
Indicates the way or mechanism by which an infection is transmitted or established from a source to a host.
-
D.
immuneEvasionMechanism
Indicates a mechanism by which an entity avoids, suppresses, or otherwise interferes with detection or elimination by an immune system.
-
E.
methodOfInfiltration
Indicates the specific technique or approach used to secretly gain access to or penetrate a target, system, or organization.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.