Triple
T29699024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChromeOS Files app |
E751429
|
entity |
| Predicate | isDefaultOn |
P33528
|
FINISHED |
| Object | Chromebook |
—
|
NE NERFINISHED |
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: Chromebook | Statement: [ChromeOS Files app, isDefaultOn, Chromebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefaultOn Context triple: [ChromeOS Files app, isDefaultOn, Chromebook]
-
A.
isDefaultFor
Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
-
B.
defaultOn
chosen
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
C.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
-
D.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
E.
isDefaultLicenseOn
Indicates that a given license is set as the default license for a particular entity or context.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b30ed88190bef8e60e45b01dd7 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:22 p.m.