Triple
T7894597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-7 |
E183314
|
entity |
| Predicate | numericRepresentation |
P48585
|
FINISHED |
| Object | two's complement |
—
|
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: two's complement | Statement: [PDP-7, numericRepresentation, two's complement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericRepresentation Context triple: [PDP-7, numericRepresentation, two's complement]
-
A.
representsDigitsOf
Indicates that one entity encodes or corresponds to the individual digits that make up the numeric value of another entity.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
bitRepresentation
chosen
Indicates that one entity is the binary (bit-level) representation or encoding of another entity.
-
D.
numericDecomposition
Indicates that a number is broken down into a set of component numbers or factors whose combination (e.g., sum or product) reconstructs the original value.
-
E.
representationType
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a15a7e88190a05474844817e5d2 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.