Triple
T6005898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptographium |
E133708
|
entity |
| Predicate | interactionWithHost |
P66544
|
FINISHED |
| Object | colonizes xylem tissues |
—
|
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: colonizes xylem tissues | Statement: [Leptographium, interactionWithHost, colonizes xylem tissues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithHost Context triple: [Leptographium, interactionWithHost, colonizes xylem tissues]
-
A.
interactionMechanism
chosen
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
B.
userInteractionModel
Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
-
C.
roleOfHost
Indicates that an entity serves as the host in relation to another entity, event, or interaction.
-
D.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
E.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f128354819088971ee398cbda77 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.