Triple
T6991861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferno |
E162102
|
entity |
| Predicate | runsOnArchitecture |
P24956
|
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: [Inferno, runsOnArchitecture, x86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsOnArchitecture Context triple: [Inferno, runsOnArchitecture, x86]
-
A.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
B.
usesArchitecture
chosen
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
C.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
D.
comparesArchitectureTo
Indicates that one entity evaluates or contrasts the structure, design, or architectural characteristics of another entity against a reference or alternative architecture.
-
E.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.