Triple
T2555361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InPrivate browsing |
E56718
|
entity |
| Predicate | activatedBy |
P6232
|
FINISHED |
| Object | opening a new InPrivate window |
—
|
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: opening a new InPrivate window | Statement: [InPrivate browsing, activatedBy, opening a new InPrivate window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatedBy Context triple: [InPrivate browsing, activatedBy, opening a new InPrivate window]
-
A.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
B.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
C.
enabledBy
chosen
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
D.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
E.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
- 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.