Triple
T8284654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP1 floating-point coprocessor |
E193759
|
entity |
| Predicate | hasRegisterFile |
P4184
|
FINISHED |
| Object | floating-point registers |
—
|
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: floating-point registers | Statement: [CP1 floating-point coprocessor, hasRegisterFile, floating-point registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegisterFile Context triple: [CP1 floating-point coprocessor, hasRegisterFile, floating-point registers]
-
A.
hasRegister
chosen
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
B.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
-
C.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
-
D.
registerFileUsed
Indicates that a particular register file is utilized or accessed in the given context or operation.
-
E.
hasAlternateRegisterSet
Indicates that an entity is associated with an additional, distinct set of registers that can be used as an alternative to its primary register set.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad0535081908bb234cfc0e32b32 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.