Triple
T30936184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Mac mini G4 |
E788128
|
entity |
| Predicate | ethernet |
P170319
|
FINISHED |
| Object | 10/100BASE-T |
—
|
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: 10/100BASE-T | Statement: [Apple Mac mini G4, ethernet, 10/100BASE-T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethernet Context triple: [Apple Mac mini G4, ethernet, 10/100BASE-T]
-
A.
energyEfficientEthernetStandard
Indicates that the subject conforms to or supports the Energy-Efficient Ethernet (EEE) standard for reducing power consumption in Ethernet networking.
-
B.
routerEthernetPorts
Indicates the association between a router and its available Ethernet ports.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or exchange.
-
E.
usesEtherType
Indicates that one network protocol or frame format employs a specific EtherType value to identify the type of payload it carries.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e5069c81908013503ba8d065d7 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:52 p.m.