Triple
T165970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi Alliance |
E3015
|
entity |
| Predicate | developsProgram |
P3324
|
FINISHED |
| Object | Wi‑Fi CERTIFIED interoperability program |
—
|
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: Wi‑Fi CERTIFIED interoperability program | Statement: [Wi‑Fi Alliance, developsProgram, Wi‑Fi CERTIFIED interoperability program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsProgram Context triple: [Wi‑Fi Alliance, developsProgram, Wi‑Fi CERTIFIED interoperability program]
-
A.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
B.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
D.
hasDevelopmentOrganization
chosen
Indicates that an entity is associated with, managed by, or supported by a specific organization responsible for its development.
-
E.
researchProgram
Indicates that an entity is engaged in, associated with, or part of a structured research initiative or program.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.