Triple
T307517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM System/360 |
E6334
|
entity |
| Predicate | standardized |
P1371
|
FINISHED |
| Object | IBM mainframe architecture |
—
|
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: IBM mainframe architecture | Statement: [IBM System/360, standardized, IBM mainframe architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardized Context triple: [IBM System/360, standardized, IBM mainframe architecture]
-
A.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
B.
standardizedBy
chosen
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
C.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
D.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
E.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.