Triple
T30405282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safari Smart App Banner |
E773460
|
entity |
| Predicate | hiddenWhen |
P95706
|
FINISHED |
| Object | user is already in the app via Universal Link |
—
|
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: user is already in the app via Universal Link | Statement: [Safari Smart App Banner, hiddenWhen, user is already in the app via Universal Link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenWhen Context triple: [Safari Smart App Banner, hiddenWhen, user is already in the app via Universal Link]
-
A.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
B.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
C.
notVisibleWhen
chosen
Indicates that one entity is not visible whenever a specified condition, state, or context involving another entity holds.
-
D.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
E.
hidesConditionFrom
Indicates that one entity intentionally conceals a condition or state from 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861d69a08190802564e3aa7d6ea7 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.