Triple
T8952433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6800 |
E213385
|
entity |
| Predicate | programCounter |
P85087
|
FINISHED |
| Object | 16-bit program counter |
—
|
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 program counter | Statement: [Motorola 6800, programCounter, 16-bit program counter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programCounter Context triple: [Motorola 6800, programCounter, 16-bit program counter]
-
A.
hasProgramCounter
chosen
Indicates that an entity is associated with a program counter, i.e., a register or mechanism that tracks the address of the next instruction to be executed.
-
B.
programSequenceNumber
Indicates the position or order of a program within a sequence or series of programs.
-
C.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
-
D.
currentProgram
Indicates that an entity is the program or process that is presently active or being executed in a given context.
-
E.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.