Triple
T264551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Surface |
E5695
|
entity |
| Predicate | supportsArchitecture |
P5090
|
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: [Microsoft Surface, supportsArchitecture, x86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsArchitecture Context triple: [Microsoft Surface, supportsArchitecture, x86]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportedPlatform
chosen
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
C.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
D.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
E.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.