Triple
T3420275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRWare Iron |
E72098
|
entity |
| Predicate | removesFeature |
P2359
|
FINISHED |
| Object | Google Chrome usage tracking |
—
|
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: Google Chrome usage tracking | Statement: [SRWare Iron, removesFeature, Google Chrome usage tracking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesFeature Context triple: [SRWare Iron, removesFeature, Google Chrome usage tracking]
-
A.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
B.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
C.
canBeRemovedBy
chosen
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
D.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
E.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.