Triple
T17483267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3u |
E425715
|
entity |
| Predicate | improvesOver |
P6555
|
FINISHED |
| Object | 10BASE-T |
—
|
NE NERFINISHED |
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: 10BASE-T | Statement: [IEEE 802.3u, improvesOver, 10BASE-T]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 10BASE-T Context triple: [IEEE 802.3u, improvesOver, 10BASE-T]
-
A.
10BASE-T
chosen
10BASE-T is an early Ethernet standard that transmits data at 10 Mbps over twisted-pair copper cabling using a star topology.
-
B.
100BASE-T4
100BASE-T4 is a Fast Ethernet standard that enables 100 Mbps data transmission over Category 3 copper cabling using four twisted pairs.
-
C.
100BASE‑TX
100BASE‑TX is a Fast Ethernet standard that delivers 100 Mbps data transmission over twisted-pair copper cabling, commonly used in local area networks.
-
D.
10BASE2
10BASE2 is an older Ethernet standard that uses thin coaxial cable to provide 10 Mbps networking over relatively short distances in a bus topology.
-
E.
10BASE5
10BASE5 is the original thick coaxial Ethernet standard that operated at 10 Mbps over relatively long cable runs and formed the basis of early wired local area networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:48 a.m.