Triple
T28601792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5170 |
E723932
|
entity |
| Predicate | defaultDisplayAdapter |
P128510
|
FINISHED |
| Object | MDA |
—
|
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: MDA | Statement: [IBM 5170, defaultDisplayAdapter, MDA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultDisplayAdapter Context triple: [IBM 5170, defaultDisplayAdapter, MDA]
-
A.
defaultAdapter
chosen
Indicates that one entity serves as the primary or standard adapter used by another entity in the absence of a specifically chosen alternative.
-
B.
defaultMediaPlayer
Indicates that an entity is designated as the primary or standard media player to be used by default for media playback.
-
C.
displayMode
Indicates how content or information is visually presented or arranged to the user.
-
D.
defaultTerminalEmulator
Indicates that one entity is configured or recognized as the standard or primary terminal emulator to be used by another entity or system.
-
E.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 4:25 a.m.