Triple
T27754886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-4 |
E701309
|
entity |
| Predicate | wordAddressable |
P163211
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PDP-4, wordAddressable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wordAddressable Context triple: [PDP-4, wordAddressable, true]
-
A.
addressingMechanism
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
B.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
-
C.
sectionAddressed
Indicates that a specific section or part of a document, text, or resource is being referred to, targeted, or dealt with by an action or statement.
-
D.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
E.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
- F. None of above. chosen
Provenance (4 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6375fa0bc8190be257d4d5eaa6dc7 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:22 p.m.