Triple
T33671831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth Time-Sharing System |
E862637
|
entity |
| Predicate | mainframeComputerUsed |
P12755
|
FINISHED |
| Object | GE-225 |
—
|
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: GE-225 | Statement: [Dartmouth Time-Sharing System, mainframeComputerUsed, GE-225]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainframeComputerUsed Context triple: [Dartmouth Time-Sharing System, mainframeComputerUsed, GE-225]
-
A.
usedInComputerFamily
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
-
B.
hasSupercomputer
Indicates that an entity possesses, controls, or is equipped with a supercomputer.
-
C.
usedInComputingSystems
Indicates that something is employed or applied within computing systems, such as hardware, software, or digital infrastructures, to perform functions or operations.
-
D.
hardwareUsedBy
chosen
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
- 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_69f6fa3ccc348190b610bc698ea184e3 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.