Triple
T33029494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relay |
E845124
|
entity |
| Predicate | messageDelivery |
P10739
|
FINISHED |
| Object | near real-time |
—
|
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: near real-time | Statement: [Relay, messageDelivery, near real-time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageDelivery Context triple: [Relay, messageDelivery, near real-time]
-
A.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
B.
deliveryMode
chosen
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
C.
messageHandling
Indicates how messages are received, processed, and responded to within a communication or messaging system.
-
D.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
E.
delivery
Indicates the act of transporting and handing over something from a sender to a recipient.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:24 a.m.