Triple
T5103242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WiMAX Forum |
E115028
|
entity |
| Predicate | certificationMark |
P58110
|
FINISHED |
| Object | WiMAX Forum Certified |
—
|
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: WiMAX Forum Certified | Statement: [WiMAX Forum, certificationMark, WiMAX Forum Certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificationMark Context triple: [WiMAX Forum, certificationMark, WiMAX Forum Certified]
-
A.
hasCertificationLabel
chosen
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
-
B.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
C.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
D.
certificationJapan
Indicates that an entity holds or is associated with a certification that is specific to or recognized in Japan.
-
E.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7586a4a08190866aea6be625837c |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.