Triple
T28613890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Mobility Center |
E724231
|
entity |
| Predicate | availabilityCondition |
P164920
|
FINISHED |
| Object | enabled by default on most mobile PCs |
—
|
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: enabled by default on most mobile PCs | Statement: [Windows Mobility Center, availabilityCondition, enabled by default on most mobile PCs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availabilityCondition Context triple: [Windows Mobility Center, availabilityCondition, enabled by default on most mobile PCs]
-
A.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
B.
availabilityType
Indicates the specific way in which something is available or offered (e.g., its mode, status, or conditions of availability) in relation to another entity.
-
C.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
D.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
E.
availabilityStart
Indicates the date and time from which something becomes available or active.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:31 a.m.