Triple
T26041082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris |
E647691
|
entity |
| Predicate | is64BitCapableHardware |
P98651
|
FINISHED |
| Object | yes (often disabled in Sempron branding) |
—
|
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: yes (often disabled in Sempron branding) | Statement: [Paris, is64BitCapableHardware, yes (often disabled in Sempron branding)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: is64BitCapableHardware Context triple: [Paris, is64BitCapableHardware, yes (often disabled in Sempron branding)]
-
A.
supportsIntel64
Indicates that one entity provides compatibility with or operational support for Intel 64-bit (x86-64) architecture in relation to another entity.
-
B.
supports64BitApps
chosen
Indicates that the subject is capable of running or is compatible with 64-bit applications.
-
C.
cpuBits
Indicates the number of bits used by a CPU’s architecture or word size in the described context.
-
D.
hasHardware
Indicates that one entity possesses, includes, or is equipped with specific hardware components or devices.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60622ddf48190b95318ea7a3676ce |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:08 a.m.