Triple
T7033140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P54C |
E163315
|
entity |
| Predicate | errataFix |
P14270
|
FINISHED |
| Object | corrected FDIV bug present in early P5 steppings |
—
|
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: corrected FDIV bug present in early P5 steppings | Statement: [P54C, errataFix, corrected FDIV bug present in early P5 steppings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errataFix Context triple: [P54C, errataFix, corrected FDIV bug present in early P5 steppings]
-
A.
requiresCorrection
Indicates that something is identified as needing modification, adjustment, or fixing to correct an error or deficiency.
-
B.
fixedBy
chosen
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
C.
canBeCorrectedBy
Indicates that something has the potential to be made accurate, fixed, or improved through the intervention or action of a specified agent or method.
-
D.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
E.
editedIn
Indicates that an entity was modified, revised, or otherwise altered within a particular context, tool, environment, or time frame.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.