Triple
T12900106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TECO |
E308589
|
entity |
| Predicate | platform |
P1292
|
FINISHED |
| Object | VAX |
E183315
|
NE 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: VAX | Statement: [TECO, platform, VAX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAX Context triple: [TECO, platform, VAX]
-
A.
VAX
chosen
VAX is a line of 32-bit minicomputers and their associated architecture developed by Digital Equipment Corporation, widely used in the late 20th century for time-sharing and scientific computing.
-
B.
VAX minicomputer
The VAX minicomputer is a line of 32-bit computers developed by Digital Equipment Corporation (DEC) that became widely used in the late 1970s and 1980s for timesharing, scientific, and business applications.
-
C.
MicroVAX
MicroVAX is a family of smaller, lower-cost minicomputers in Digital Equipment Corporation’s VAX line, designed to bring VAX architecture to departmental and office environments.
-
D.
Prime Computer
Prime Computer was a U.S. minicomputer manufacturer prominent in the 1970s and 1980s, known for its PRIMOS operating system and 16-bit and 32-bit business systems.
-
E.
IBM VSE
IBM VSE is an IBM mainframe operating system designed for smaller and midrange systems, focused on batch and transaction processing in business environments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a56189b081909ed838addcb6d265 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:40 p.m.