Triple
T27657650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R3 (PDP-11 register) |
E697035
|
entity |
| Predicate | dataPathRole |
P100711
|
FINISHED |
| Object | source operand register |
—
|
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: source operand register | Statement: [R3 (PDP-11 register), dataPathRole, source operand register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPathRole Context triple: [R3 (PDP-11 register), dataPathRole, source operand register]
-
A.
roleInPath
chosen
Indicates that an entity participates in a specific path or route by occupying a particular role or position within that path.
-
B.
associatedDataRole
Indicates that one entity has a specific role in relation to data that is linked or connected to another entity.
-
C.
dataPathLength
Indicates the length or distance of a specified data path within a data structure, system, or network.
-
D.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
-
E.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:35 p.m.