Triple
T38309522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regor (cut-down) |
E1033645
|
entity |
| Predicate | supportsInstructionSetArchitecture |
P78644
|
FINISHED |
| Object | x86-64 |
—
|
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: x86-64 | Statement: [Regor (cut-down), supportsInstructionSetArchitecture, x86-64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInstructionSetArchitecture Context triple: [Regor (cut-down), supportsInstructionSetArchitecture, x86-64]
-
A.
hasInstructionSet
chosen
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
B.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
C.
hasArchitecturalSupport
Indicates that one entity provides structural or design backing, compatibility, or enablement for another within an architectural context.
-
D.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
E.
supportedCPU
Indicates that a given CPU model or architecture is compatible with and can be used by a particular system, device, or software.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.