Triple
T22028117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jitsi |
E544016
|
entity |
| Predicate | supportsProtocol |
P203
|
FINISHED |
| Object | SIP |
—
|
NE NERFINISHED |
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: SIP | Statement: [Jitsi, supportsProtocol, SIP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SIP Context triple: [Jitsi, supportsProtocol, SIP]
-
A.
SIP
SIP is the IATA airport code for Simferopol International Airport, the main air gateway to the Crimean Peninsula.
-
B.
SIP
SIP is a Unicode supplementary plane that contains additional CJK ideographs beyond those in the Basic Multilingual Plane.
-
C.
SIP
SIP is a macOS security technology that restricts system-level modifications to protect the operating system from malware and accidental damage.
-
D.
SIP
SIP is the National Rail station code for Shipton railway station in Oxfordshire, England.
-
E.
Session Initiation Protocol
chosen
Session Initiation Protocol (SIP) is a signaling protocol used to establish, modify, and terminate real-time communication sessions such as voice and video calls over IP networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 8:24 p.m.