Triple
T8952434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6800 |
E213385
|
entity |
| Predicate | statusRegister |
P85845
|
FINISHED |
| Object | condition code register |
—
|
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: condition code register | Statement: [Motorola 6800, statusRegister, condition code register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRegister Context triple: [Motorola 6800, statusRegister, condition code register]
-
A.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
B.
statusWordRegister
Indicates the level of formality or social register associated with a status-related word in language use.
-
C.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
-
D.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
E.
officialRegisterOf
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 6:59 p.m.