Triple
T2979413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3an-2006 |
E80474
|
entity |
| Predicate | definesApplication |
P44386
|
FINISHED |
| Object | 10GBASE-T LAN applications |
—
|
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: 10GBASE-T LAN applications | Statement: [IEEE 802.3an-2006, definesApplication, 10GBASE-T LAN applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesApplication Context triple: [IEEE 802.3an-2006, definesApplication, 10GBASE-T LAN applications]
-
A.
applicationLocation
Indicates the place or environment where an application is deployed, used, or made available.
-
B.
requiresApplicationTo
Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
-
C.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999cca40819082e2d6d10bdb7872 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.