Triple
T12035406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 604 |
E286523
|
entity |
| Predicate | arithmeticOperations |
P819
|
FINISHED |
| Object | addition |
—
|
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: addition | Statement: [IBM 604, arithmeticOperations, addition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arithmeticOperations Context triple: [IBM 604, arithmeticOperations, addition]
-
A.
arithmetic
Indicates a relationship where one entity performs or represents a mathematical operation (such as addition, subtraction, multiplication, or division) involving one or more other entities.
-
B.
isArithmetic
Indicates that something pertains to arithmetic operations, properties, or reasoning within the domain of numbers and basic calculations.
-
C.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
-
D.
typeOfOperation
chosen
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
E.
operatorSymbol
Indicates the symbolic notation used to represent an operator in an expression or formal system.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.