Triple
T7920727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-11 |
E183936
|
entity |
| Predicate | hasAddressSpace |
P3700
|
FINISHED |
| Object | 16-bit address space |
—
|
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: 16-bit address space | Statement: [PDP-11, hasAddressSpace, 16-bit address space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressSpace Context triple: [PDP-11, hasAddressSpace, 16-bit address space]
-
A.
addressSpaceSize
chosen
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
B.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
C.
hasCodeSpaceSize
Indicates the size or capacity of the code space associated with an entity, such as the range or number of distinct codes it can represent.
-
D.
hasPublicAddressSystem
Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
-
E.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9360f881908ca2433d0623315b |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.