Triple
T2693920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100BASE‑TX |
E58466
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | 100BASE-TX |
E58466
|
NE 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: 100BASE-TX | Statement: [100BASE‑TX, alsoKnownAs, 100BASE-TX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 100BASE-TX Context triple: [100BASE‑TX, alsoKnownAs, 100BASE-TX]
-
A.
100BASE‑TX
chosen
100BASE‑TX is a Fast Ethernet standard that delivers 100 Mbps data transmission over twisted-pair copper cabling, commonly used in local area networks.
-
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.
10BASE-T
10BASE-T is an early Ethernet standard that transmits data at 10 Mbps over twisted-pair copper cabling using a star topology.
-
D.
100BASE-X
100BASE-X is a family of Fast Ethernet standards that define 100 Mbit/s transmission over fiber optic or twisted-pair cabling using 4B/5B line coding.
-
E.
IEEE 802.3ab
IEEE 802.3ab is an Ethernet networking standard that defines 1000BASE-T Gigabit Ethernet over Category 5 (and better) twisted-pair copper cabling.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0f43b08190a5abd936b14603b7 |
completed | March 7, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf6804b48190ac0bfe464da93025 |
completed | March 10, 2026, 5:43 a.m. |
Created at: March 6, 2026, 9:54 p.m.