Triple
T28608030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R2000 |
E724104
|
entity |
| Predicate | registerFileType |
P166883
|
FINISHED |
| Object | general-purpose register file |
—
|
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: general-purpose register file | Statement: [R2000, registerFileType, general-purpose register file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerFileType Context triple: [R2000, registerFileType, general-purpose register file]
-
A.
registerFile
Indicates that an entity records or stores information about a file in some kind of registry or tracking system.
-
B.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
C.
replacesFileType
Indicates that one file type is substituted for or takes the place of another file type.
-
D.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
E.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
- F. None of above. chosen
Provenance (4 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:28 a.m.