Triple
T2555351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InPrivate browsing |
E56718
|
entity |
| Predicate | dataDeletedWhen |
P31792
|
FINISHED |
| Object | InPrivate window is closed |
—
|
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: InPrivate window is closed | Statement: [InPrivate browsing, dataDeletedWhen, InPrivate window is closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataDeletedWhen Context triple: [InPrivate browsing, dataDeletedWhen, InPrivate window is closed]
-
A.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
B.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
C.
dateOfLoss
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
-
D.
removalPeriod
chosen
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.