Triple
T17417121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VoIP |
E423515
|
entity |
| Predicate | canInteroperateWith |
P48644
|
FINISHED |
| Object | PSTN via gateways |
—
|
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: PSTN via gateways | Statement: [VoIP, canInteroperateWith, PSTN via gateways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInteroperateWith Context triple: [VoIP, canInteroperateWith, PSTN via gateways]
-
A.
interoperabilityWith
chosen
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
B.
canCoexistWith
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
C.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
-
D.
hasCrossPlatformInterchange
Indicates that there is a transfer point where passengers can switch between different transportation platforms or modes within the same location.
-
E.
isGenerallyCompatibleWith
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44233c7888190a4d2aa703b206851 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.