Triple
T3872144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascaris lumbricoides |
E92410
|
entity |
| Predicate | infects |
P6647
|
FINISHED |
| Object | human small intestine |
—
|
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: human small intestine | Statement: [Ascaris lumbricoides, infects, human small intestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infects Context triple: [Ascaris lumbricoides, infects, human small intestine]
-
A.
infectsTissue
chosen
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
-
B.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
C.
colonizes
Indicates that one entity establishes control or settlement over another entity’s territory or domain, often imposing its presence, systems, or influence there.
-
D.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of another entity.
-
E.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.