Triple
T5945452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 7090 ALGOL compiler |
E132267
|
entity |
| Predicate | computerType |
P15304
|
FINISHED |
| Object | mainframe computer |
—
|
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: mainframe computer | Statement: [IBM 7090 ALGOL compiler, computerType, mainframe computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computerType Context triple: [IBM 7090 ALGOL compiler, computerType, mainframe computer]
-
A.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
B.
systemType
chosen
Indicates the classification or category of a system that an entity belongs to or operates as.
-
C.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
-
D.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
E.
usedComputerRankings
Indicates that the selection or decision was based on rankings generated by a computer 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.