Triple
T22028311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instant Hotspot |
E544020
|
entity |
| Predicate | connectsDevices |
P13458
|
FINISHED |
| Object | nearby Apple devices signed in to the same Apple ID |
—
|
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: nearby Apple devices signed in to the same Apple ID | Statement: [Instant Hotspot, connectsDevices, nearby Apple devices signed in to the same Apple ID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsDevices Context triple: [Instant Hotspot, connectsDevices, nearby Apple devices signed in to the same Apple ID]
-
A.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
B.
connectsSystem
Indicates that one system establishes a link or interface with another system, enabling interaction or data exchange between them.
-
C.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
D.
relatedDevice
chosen
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
E.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.