Triple
T4567055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi CERTIFIED Enhanced Open |
E121934
|
entity |
| Predicate | requiresUserAuthentication |
P30774
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Wi‑Fi CERTIFIED Enhanced Open, requiresUserAuthentication, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresUserAuthentication Context triple: [Wi‑Fi CERTIFIED Enhanced Open, requiresUserAuthentication, false]
-
A.
authenticationRequired
chosen
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
-
B.
requiresStatus
Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
-
C.
requiresClaim
Indicates that one entity can only be accessed, used, or fulfilled if a specific claim or entitlement has first been asserted or verified.
-
D.
requiresSubscription
Indicates that access to or use of something is conditional on having an active subscription.
-
E.
requiresRole
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
- 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_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. |
Created at: March 20, 2026, 1:09 p.m.