Triple
T4567061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi CERTIFIED Enhanced Open |
E121934
|
entity |
| Predicate | targetsUseCase |
P57747
|
FINISHED |
| Object | guest Wi‑Fi access |
—
|
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: guest Wi‑Fi access | Statement: [Wi‑Fi CERTIFIED Enhanced Open, targetsUseCase, guest Wi‑Fi access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsUseCase Context triple: [Wi‑Fi CERTIFIED Enhanced Open, targetsUseCase, guest Wi‑Fi access]
-
A.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
targetWork
Indicates that one entity is the specific work (e.g., document, artwork, or project) that another entity is directed at, refers to, or is primarily concerned with.
-
D.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
E.
targetsSector
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589e35808190aa609bb04b128dbe |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.