Triple
T712611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Chrome Canary |
E14242
|
entity |
| Predicate | softwareQuality |
P6861
|
FINISHED |
| Object | experimental |
—
|
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: experimental | Statement: [Google Chrome Canary, softwareQuality, experimental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareQuality Context triple: [Google Chrome Canary, softwareQuality, experimental]
-
A.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
B.
quality
chosen
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
-
C.
softwareExperience
Indicates the level or extent of a person's prior experience working with or using specific software.
-
D.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
E.
code
Indicates that an entity writes, develops, or produces computer software or source code.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.