Triple
T8918236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMDE |
E212345
|
entity |
| Predicate | previouslySupportedPlatform |
P79648
|
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: [LMDE, previouslySupportedPlatform, x86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslySupportedPlatform Context triple: [LMDE, previouslySupportedPlatform, x86]
-
A.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
-
B.
previouslySupportedHardware
chosen
Indicates that the subject hardware was supported in the past but is no longer currently supported.
-
C.
previouslySupportedVersion
Indicates that one entity was a supported version of another entity at some time in the past but is no longer the current supported version.
-
D.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.