Triple
T166008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi Alliance |
E3015
|
entity |
| Predicate | hasMainClassification |
P2767
|
FINISHED |
| Object | Wi‑Fi industry consortium |
—
|
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 industry consortium | Statement: [Wi‑Fi Alliance, hasMainClassification, Wi‑Fi industry consortium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainClassification Context triple: [Wi‑Fi Alliance, hasMainClassification, Wi‑Fi industry consortium]
-
A.
hasMajorCategory
chosen
Indicates that something is associated with or classified under a primary, overarching category.
-
B.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
C.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
- 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.