Triple
T8285555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QEMU |
E193779
|
entity |
| Predicate | supportsGuestArchitecture |
P82507
|
FINISHED |
| Object | x86 |
—
|
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 | Statement: [QEMU, supportsGuestArchitecture, x86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGuestArchitecture Context triple: [QEMU, supportsGuestArchitecture, x86]
-
A.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
B.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
-
C.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
-
D.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
E.
supportsIntel64
Indicates that one entity provides compatibility with or operational support for Intel 64-bit (x86-64) architecture in relation to 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad20ae481908179aba245c73fad |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.