Triple
T9497066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WRQ |
E229035
|
entity |
| Predicate | hasOpcode |
P88949
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [WRQ, hasOpcode, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpcode Context triple: [WRQ, hasOpcode, 2]
-
A.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
hasBinaryOperation
Indicates that there exists a binary operation defined on the related entity or between the related entities, combining two inputs to produce a single output.
-
C.
hasConditionCodes
Indicates that an entity is associated with one or more standardized condition codes describing its state, status, or circumstances.
-
D.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
E.
hasOpalType
Indicates that an entity is associated with or classified by a specific type of opal.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ecf4148190aa8f4733980166ae |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.