Triple
T22027805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STUN |
E544009
|
entity |
| Predicate | clientRole |
P78653
|
FINISHED |
| Object | sends binding requests to STUN server |
—
|
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: sends binding requests to STUN server | Statement: [STUN, clientRole, sends binding requests to STUN server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientRole Context triple: [STUN, clientRole, sends binding requests to STUN server]
-
A.
ClientRole
chosen
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
B.
catalogRole
Indicates that an entity holds a specific functional role or responsibility within the context of a catalog or cataloging system.
-
C.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
D.
siteRole
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
E.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
- 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_69f127cdf5c08190ac804664d6e56fe2 |
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.