Triple
T30314942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mach 3.0 |
E771034
|
entity |
| Predicate | hasCommunicationModel |
P112150
|
FINISHED |
| Object | asynchronous message passing |
—
|
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: asynchronous message passing | Statement: [Mach 3.0, hasCommunicationModel, asynchronous message passing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunicationModel Context triple: [Mach 3.0, hasCommunicationModel, asynchronous message passing]
-
A.
hasCommunicationClass
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
B.
hasCommunicationType
chosen
Indicates that one entity uses, supports, or is associated with a particular form or mode 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.
hasCommunicationInterface
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.
-
E.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
Created at: April 29, 2026, 7:51 p.m.