Triple
T22027068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Session Traversal Utilities for NAT |
E543994
|
entity |
| Predicate | usesMessageType |
P112150
|
FINISHED |
| Object | Binding Request |
—
|
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: Binding Request | Statement: [Session Traversal Utilities for NAT, usesMessageType, Binding Request]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMessageType Context triple: [Session Traversal Utilities for NAT, usesMessageType, Binding Request]
-
A.
relatedMessageType
Indicates that one message is associated with another by specifying the type or category of that related message.
-
B.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
C.
hasCommunicationType
chosen
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
D.
precedesMessageType
Indicates that one message type must occur or be processed before another specified message type.
-
E.
hasMessagingFeatures
Indicates that an entity provides or supports messaging-related capabilities or functions.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.