Triple
T7492396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Switched Telephone Network |
E177035
|
entity |
| Predicate | usesSwitchingType |
P69214
|
FINISHED |
| Object | circuit switching |
—
|
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: circuit switching | Statement: [Public Switched Telephone Network, usesSwitchingType, circuit switching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSwitchingType Context triple: [Public Switched Telephone Network, usesSwitchingType, circuit switching]
-
A.
usedByRegimeType
Indicates that something (such as a method, policy, or tool) is employed or implemented by a particular type of political regime.
-
B.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
C.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
D.
usesCircuitType
chosen
Indicates that one entity employs or is implemented using a specific type of circuit.
-
E.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:43 p.m.