Triple
T30376316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEEP |
E772697
|
entity |
| Predicate | messageOrientation |
P77331
|
FINISHED |
| Object | binary framing with arbitrary payload |
—
|
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: binary framing with arbitrary payload | Statement: [BEEP, messageOrientation, binary framing with arbitrary payload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageOrientation Context triple: [BEEP, messageOrientation, binary framing with arbitrary payload]
-
A.
communicationDirection
Indicates the directional flow of a communication act, specifying who is sending information and who is receiving it.
-
B.
messageSpace
Indicates a relationship where one entity provides or occupies a space or channel through which messages can be sent, stored, or exchanged between parties.
-
C.
messageHandling
Indicates how messages are received, processed, and responded to within a communication or messaging system.
-
D.
orientationType
chosen
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
E.
synchronizationDirection
Indicates the direction in which data or state is synchronized between related entities (e.g., one-way or bidirectional).
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68513cbf881908ec5f924484b19b9 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8 p.m.