Triple
T26176692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF |
E654561
|
entity |
| Predicate | registerClass |
P158292
|
FINISHED |
| Object | general-purpose register pair |
—
|
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 pair | Statement: [AF, registerClass, general-purpose register pair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerClass Context triple: [AF, registerClass, general-purpose register pair]
-
A.
addsRegisterClass
chosen
Indicates that one entity assigns or associates a specific register class with another entity, typically extending or modifying its register-related behavior.
-
B.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
C.
addsClass
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
-
D.
registerModel
Indicates the action of adding or enrolling a model into a system or registry so it becomes recognized and available for use.
-
E.
addsProtectedClass
Indicates that an action or rule introduces a new protected class or category into a set of legally or formally safeguarded groups.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:38 p.m.