Triple
T33671866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth Time-Sharing System |
E862637
|
entity |
| Predicate | networkingMethod |
P15300
|
FINISHED |
| Object | dial-up telephone lines |
—
|
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: dial-up telephone lines | Statement: [Dartmouth Time-Sharing System, networkingMethod, dial-up telephone lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkingMethod Context triple: [Dartmouth Time-Sharing System, networkingMethod, dial-up telephone lines]
-
A.
networkingOptions
Indicates the available ways entities can establish, configure, or use network connections or communication channels between them.
-
B.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
connectionEstablishmentMethod
chosen
Indicates the method or mechanism by which a connection between entities is initiated or established.
-
D.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or exchange.
-
E.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:43 a.m.