Triple
T32343028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-12 |
E826369
|
entity |
| Predicate | hasDisplayDevice |
P178358
|
FINISHED |
| Object | CRT display |
—
|
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: CRT display | Statement: [PDP-12, hasDisplayDevice, CRT display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayDevice Context triple: [PDP-12, hasDisplayDevice, CRT display]
-
A.
hasPhysicalDisplays
Indicates that an entity possesses one or more tangible, visible display units or interfaces.
-
B.
hasOutputDevice
chosen
Indicates that an entity is connected to or equipped with a particular output device used to present information or results.
-
C.
canBeDisplayedOn
Indicates that something is capable of being shown or rendered on a particular medium, device, or interface.
-
D.
displayDevice
Indicates that one entity functions as a device used to visually present or output information from another entity.
-
E.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 1, 2026, 12:48 a.m.