Triple
T20657916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3by |
E507675
|
entity |
| Predicate | definesMedium |
P127625
|
FINISHED |
| Object | multimode fiber |
—
|
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: multimode fiber | Statement: [IEEE 802.3by, definesMedium, multimode fiber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMedium Context triple: [IEEE 802.3by, definesMedium, multimode fiber]
-
A.
definesMediumType
chosen
Indicates that one entity specifies or assigns the medium type or format category of another entity.
-
B.
canonicalMedium
Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
-
C.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
D.
introducedInMedium
Indicates that an entity first appears or is initially presented within a specified medium (such as a book, film, game, or other format).
-
E.
targetMedium
Indicates the medium or channel through which an action, message, or effect is directed or intended to be delivered.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.