Triple
T8570609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-100 bus computers |
E202915
|
entity |
| Predicate | commonOS |
P1593
|
FINISHED |
| Object | MP/M |
E713571
|
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: MP/M | Statement: [S-100 bus computers, commonOS, MP/M]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MP/M Context triple: [S-100 bus computers, commonOS, MP/M]
-
A.
MP/M
chosen
MP/M is a multi-user, multitasking operating system developed by Gary Kildall as an advanced, multi-terminal extension of CP/M for microcomputers.
-
B.
MP/M operating system
MP/M operating system is a multi-user, multitasking variant of CP/M designed for microcomputers, created by computer scientist and software pioneer Gary Kildall.
-
C.
MP
MP is the reporting mark for the Missouri Pacific Railroad, a major former U.S. Class I railroad that operated across the Midwest and Southwest.
-
D.
MP
MP is the two-letter ISO 3166-1 alpha-2 country code assigned to the Northern Mariana Islands.
-
E.
MP
MP is the vehicle registration code for the Indian state of Madhya Pradesh.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc457ab8b08190a53c730417288deb |
completed | March 31, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce8983bd3c819094457b5160bc928d |
completed | April 2, 2026, 3:21 p.m. |
Created at: March 30, 2026, 6:21 p.m.