Triple
T27866200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-9 |
E704365
|
entity |
| Predicate | supportsIndexRegisters |
P201774
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PDP-9, supportsIndexRegisters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIndexRegisters Context triple: [PDP-9, supportsIndexRegisters, yes]
-
A.
numberOfIndexRegisters
Indicates the quantity of index registers associated with or available to a given entity (such as a processor or instruction set).
-
B.
numberOfRegisters
Indicates the total count of registers associated with or contained in a given entity.
-
C.
supports32BitRegistersViaPairing
Indicates that the system can handle 32-bit registers by pairing smaller-width registers together to emulate 32-bit behavior.
-
D.
registersUsed
Indicates that certain registers are utilized or occupied by a given operation, instruction, or computational entity.
-
E.
numberOfGeneralPurposeRegisters
Indicates the quantity of general-purpose registers associated with or available in a given computing context.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
| PDg | Predicate description generation | batch_6a00210313c08190ab581c505ef46b8e |
completed | May 10, 2026, 6:09 a.m. |
Created at: April 27, 2026, 6:21 p.m.