Triple
T29938554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horovod |
E760433
|
entity |
| Predicate | usesCommunicationBackend |
P34297
|
FINISHED |
| Object | MPI |
—
|
NE NERFINISHED |
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: MPI | Statement: [Horovod, usesCommunicationBackend, MPI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationBackend Context triple: [Horovod, usesCommunicationBackend, MPI]
-
A.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
B.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
-
C.
hasCommunicationAccess
Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
-
D.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
E.
hasCommunicationInterface
chosen
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 6:21 p.m.