Triple
T26399619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.245 |
E663662
|
entity |
| Predicate | roleInH.323 |
P57746
|
FINISHED |
| Object | control signaling between endpoints |
—
|
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: control signaling between endpoints | Statement: [H.245, roleInH.323, control signaling between endpoints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInH.323 Context triple: [H.245, roleInH.323, control signaling between endpoints]
-
A.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
B.
roleInZoom
Indicates that an entity has a specific role or function within a Zoom meeting or Zoom-related context.
-
C.
roleInProtocolStack
chosen
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
D.
memberRole_3
Indicates that an entity holds a specific role or position as a member within a group, organization, or context.
-
E.
roleInWPA3
Indicates that an entity holds a specific role or function within the WPA3 (Wi‑Fi Protected Access 3) security protocol or framework.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 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 26, 2026, 11:31 p.m.