Triple
T3426985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Search |
E72248
|
entity |
| Predicate | offersSetting |
P9404
|
FINISHED |
| Object | incognito search via browser |
—
|
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: incognito search via browser | Statement: [Google Search, offersSetting, incognito search via browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSetting Context triple: [Google Search, offersSetting, incognito search via browser]
-
A.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
B.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
C.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
-
D.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
E.
offersSolution
Indicates that one entity provides or proposes a remedy, answer, or way to resolve a problem or need experienced by another entity.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb982792c8190b1163eee4252210f |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.