Triple
T22443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.11 |
E445
|
entity |
| Predicate | firstStandardApproved |
P1686
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [IEEE 802.11, firstStandardApproved, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStandardApproved Context triple: [IEEE 802.11, firstStandardApproved, 1997]
-
A.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
firstAwarded
Indicates the time or occasion when an award, honor, or recognition was given for the very first time.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24654724481909ba14b7f68d2a472 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a246e7fac481909b0c500d4500650e |
completed | Feb. 28, 2026, 1:37 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.