Triple
T6833322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i |
E157389
|
entity |
| Predicate | additiveInverse |
P21101
|
FINISHED |
| Object | -i |
—
|
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: -i | Statement: [i, additiveInverse, -i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additiveInverse Context triple: [i, additiveInverse, -i]
-
A.
oppositeNumber
chosen
Indicates that one number is the additive inverse of the other, such that their sum equals zero.
-
B.
hasAdditiveInverses
Indicates that for every element in a given structure, there exists another element that combines with it under the operation to yield the additive identity (typically zero).
-
C.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
D.
hasOppositeNumberForm
Indicates that one entity is represented by a number form that is the opposite (e.g., additive vs. subtractive, positive vs. negative, or otherwise contrastive) of the number form used to represent the other entity.
-
E.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.