Triple
T16501621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxyuridae |
E400812
|
entity |
| Predicate | hostInteraction |
P80430
|
FINISHED |
| Object | can cause pruritus ani in humans |
—
|
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: can cause pruritus ani in humans | Statement: [Oxyuridae, hostInteraction, can cause pruritus ani in humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostInteraction Context triple: [Oxyuridae, hostInteraction, can cause pruritus ani in humans]
-
A.
interactionWithHumans
chosen
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
B.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
C.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
D.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
E.
userInteractionModel
Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4f7b7c8190adb5a113f798484f |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.