Triple
T35203894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xfinity WiFi |
E1016481
|
entity |
| Predicate | hasHotspotSSID |
P195253
|
FINISHED |
| Object | xfinitywifi |
—
|
NE NERFINISHED |
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: xfinitywifi | Statement: [Xfinity WiFi, hasHotspotSSID, xfinitywifi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHotspotSSID Context triple: [Xfinity WiFi, hasHotspotSSID, xfinitywifi]
-
A.
wifiAvailable
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
B.
hasModernAccessPoint
Indicates that one entity provides or includes a contemporary means or facility through which another entity can be accessed or used.
-
C.
isHotspotTrackOf
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
D.
usesWiFiHotspotsOf
Indicates that one entity connects to and accesses the internet through WiFi hotspots provided, owned, or managed by another entity.
-
E.
hasBuiltInWiFi
Indicates that the subject device or system includes integrated Wi-Fi capability without requiring external hardware.
- F. None of above. chosen
Provenance (4 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 3, 2026, 4:02 p.m.