Triple
T22814310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifest V2 |
E565060
|
entity |
| Predicate | statusInChromeWebStore |
P107866
|
FINISHED |
| Object | phased out for new extensions |
—
|
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: phased out for new extensions | Statement: [Manifest V2, statusInChromeWebStore, phased out for new extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInChromeWebStore Context triple: [Manifest V2, statusInChromeWebStore, phased out for new extensions]
-
A.
statusInChrome
chosen
Indicates the current state or condition of something specifically within the context of the Chrome browser.
-
B.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusInWindows11
Indicates the status or condition of something specifically within the context of the Windows 11 operating system.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.